note(canon): pre-claim — M2.1 deploy verified live read-only (/etc/cc-ci pulled to 3bdd5d1, weekly timer deployed, sweep runs non-hollow path); M2 not yet claimed

machine-docs/REVIEW-canon.md

@@ -150,3 +150,24 @@ benign re-run, not a divergence — the recorded version/commit are correct eith
 **Verdict: M1 PASS.** No VETO. All M1 DoD items cold-verified; the deployed-state items (M1.4 live,
 M1.5 timer schedule) are honestly scoped by the Builder to M2 and I will hold them there. (Consulted
 JOURNAL-canon.md only AFTER writing this verdict: no surprises — confirms the proof-A/C sequence.)
+
+---
+
+## Pre-claim observation @ 2026-06-17T07:23Z — M2.1 deploy verified live (NOT a gate verdict)
+
+Builder inbox: M1 PASS consumed; M2.1 deploy done; M2.2 full sweep started (long, serial, hours).
+M2 NOT yet claimed — no formal verdict here, just an opportunistic READ-ONLY check that resolves my
+two carried-to-M2 code-only probes (favorable; I'll still re-verify the live proofs at the M2 claim):
+- **/etc/cc-ci now at `3bdd5d1`** (current main; was stale `e60415d` Phase-3 era), with `tests/` +
+  `runner/nightly_sweep.py` present → the deploy DID `git -C /etc/cc-ci pull`. My M1.4 "deploy must
+  pull or stays hollow" risk is cleared.
+- **Deployed timer:** `systemctl cat nightly-sweep.timer` → `OnCalendar=Sun *-*-* 03:00:00`,
+  `Persistent=true` (weekly, live). M1.5 deployed-schedule probe cleared.
+- **Deployed code path is the non-hollow one:** the in-flight sweep (PID 1620630) runs
+  `nightly_sweep.sweep()` from `/etc/cc-ci/runner`, and `run_recipe_ci.py` runs from
+  `/etc/cc-ci/runner/` — i.e. the checkout WITH `tests/`, not the store copy. Root cause fixed live.
+STILL OWED at the M2 claim (I will cold-verify, not trust the sweep log): canonicals actually promoted
+for greens / reds left intact / no-new-tag skipped (M2.2); run-twice→skip-all (M2.3); live tagged-vs-
+untagged (M2.4); real timer fire advances canonicals via full main() incl. roll (M2.5); samever never
+fires in-sweep (M2.6); disk budget recorded (M2.7); §2.G UPGRADE_BASE_VERSION retirement (M2.8).
+Staying read-only while the sweep is in flight (single node).