docs: architect on 2.1.276 too — the fleet has one CLI version

Co-Authored-By: Claude Opus 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01WZb5A2kfVfjpdwSochkuHz

docs/NEXT-SESSION.md

@@ -109,8 +109,9 @@ guessed family.
 2. ~~**microVM tier is unexercised since v0.8.5.**~~ Closed 2026-09-18: three
    VM missions on Claude Code 2.1.276 — claude `01a0b75e`, glm `01a0b761`,
    kimi `01a0b768` — 28/28 checks including provider egress proof. See the
-   addendum. Still open from it: architect's `claude` rootfs is 2.1.223 by
-   choice (drain it or rebuild before a claude VM mission that must be 276).
+   addendum. architect rebuilt to 2.1.276 the same evening (claude +
+   local-ornith, selftest real turn PASS), so placement no longer decides the
+   CLI version.
 3. **`files` is n=3.** 7 of 9 is a signal. `structured-paper-summary` went
    unread in 2 of the last 3 runs; the skills section sits 87–90% into the
    prompt. Position is the untested lever.
@@ -208,9 +209,10 @@ verifier's tool restriction was plausibly never applied. Fixed (`cbc9c2d`).
 `"anthropic"`: a glm mission is now judged by the subscription and honestly
 `independent=true` (`claude-opus-5`); before, glm would have judged glm.
 
-Fleet facts: architect untouched (claude 2.1.223, local-ornith 2.1.223) by
-operator choice — a `claude` VM mission's CLI depends on placement until it is
-rebuilt; `rootfs-*.ext4.pre276` backups on tank (~7 GB, delete after sign-off);
+Fleet facts: both nodes on 2.1.276 (architect rebuilt later the same day —
+its cargo builds into `/hot/targets/_default`, so pass `FC_AGENT_BIN`);
+`rootfs-*.ext4.pre276` backups on tank (~7 GB) and architect (~4 GB), delete
+after sign-off;
 `rootfs-canary-claude.ext4.promoted-2.1.276` kept as the next candidate slot.
 Judge spend this week after the runs: 85 z.ai requests. Prod holds 8 missions,
 all ours.