Panama learns what a server is: from a root login to running containers

A machine's role is now the interview's first question and the one answer
Panama records. Servers get the same shell minus the screen: core packages,
nvm, Bun, Claude Code and Codex (desktops get Codex too), linger, rootless
ports from 80, firewalld, the nginx-bridge network, and a nightly image
updater that replaced watchtower for cause.

server/containers/ carries junior's 23 compose services -- secrets moved to
per-machine .env files that never enter this public repo, every transformed
compose proven to render byte-identical to what is live. 'panama server'
enables, disables and relinks them; nothing here restarts a running service.
'boot --server' walks a fresh VPS from its root login to a normal install.

Five new contracts pin the secrets rule, the catalog's shape, panama-server's
behavior, the role plumbing, and the dotfile classification.

Claude-Session: https://claude.ai/code/session_01NU5JGiN3JfzqrLQB6wmJ1E

setup/scripts/link-server

@@ -0,0 +1,15 @@
+#!/usr/bin/env bash
+
+# The server counterpart of link-dotfiles, and deliberately thin: ~/Server is
+# created here, and everything about which services are linked into it is
+# panama-server's job -- relink refreshes the symlinks of whatever this
+# machine has enabled, and enabling something new is a decision a person makes
+# with `panama server enable`, not something an installer infers.
+
+set -euo pipefail
+
+PANAMA_PATH="${PANAMA_PATH:-$HOME/.local/share/Panama}"
+
+mkdir -p "$HOME/Server"
+
+exec "$PANAMA_PATH/bin/panama-server" relink