Fix: Teach the update contract about the link-mcp stage

tests/setup/update-command-contract

@@ -36,7 +36,7 @@ note() { findings+=("$1"); }
 tmp="$(mktemp -d -t panama-update-contract.XXXXXX)"
 trap 'rm -rf "$tmp"' EXIT
 
-STAGE_NAMES=(install-packages link-dotfiles link-skills link-user change-settings
+STAGE_NAMES=(install-packages link-dotfiles link-skills link-user link-mcp change-settings
              link-vicinae-scripts setup-server link-server setup-identity
              install-hardware)
 PACKAGE_BEHAVIOR_INPUTS=(
@@ -191,7 +191,7 @@ fi
 
 # ── 2. Exactly the answer-free stages ────────────────────────────────────────
 
-for stage in install-packages link-dotfiles link-skills link-user change-settings link-vicinae-scripts; do
+for stage in install-packages link-dotfiles link-skills link-user link-mcp change-settings link-vicinae-scripts; do
     grep -qx "$stage" <<<"$ran" || note "install --upgrade did not run $stage"
 done
 for stage in setup-identity install-hardware; do
@@ -364,7 +364,7 @@ grep -qx 'link-dotfiles' "$tmp/c/ran" \
 # reason to abandon the machine either. It suppresses the stages that open DNF
 # and the migrations, which are free to run a transaction of their own. Every
 # stage that only links configuration still runs, and the status stays 78.
-SAFE_STAGES=(link-dotfiles link-skills link-user link-vicinae-scripts)
+SAFE_STAGES=(link-dotfiles link-skills link-user link-mcp link-vicinae-scripts)
 DNF_SUPPRESSED=(install-packages change-settings install-hardware)
 
 assert_trust_refusal() {