status(canon): M2.2 run-1 surfaced+fixed promote bug; validating faithful-install fix

machine-docs/STATUS-canon.md

@@ -98,8 +98,22 @@ read the module; deployed-timer check is M2.
 ### Out of M1 scope (M2): full multi-recipe sweep e2e, run-twice determinism, real timer fire, samever
 orthogonality live, disk budget, §2.G UPGRADE_BASE_VERSION retirement.
 
+- **M2.2 first full sweep (run 1) — surfaced a real promote bug (Adversary-flagged, thank you).**
+  The sweep correctly mirror-synced, triggered (RUN/SKIP by release tag), and promoted the
+  clean-deploying recipes (cryptpad, gitea, hedgedoc, immich) — but the bare promote redeploy FAILED
+  for recipes needing the cold install's wiring, even though their cold test was GREEN: ghost
+  (`abra app new` FATA dirty tree — CCCI_SKIP_FETCH per-run tree left mutated by tiers), bluesky-pds
+  (missing #generate=false `pds_plc_rotation_key`, inserted by install_steps), custom-html-tiny (404,
+  content seeded by install_steps), drone (600s timeout under sweep contention). Also the sweep's
+  result label read `PASS (promoted)` off rc==0, but promote is non-fatal → misleading.
+- **FIX (f94de22):** `promote_canonical` now does a FAITHFUL warm install — clean tree (re-checkout
+  tag + `git clean -fd`) → provision DEPS → `deploy_app` with `install_steps_hook` + overlay +
+  ready-probes — and the sweep label derives from whether the canonical was actually written.
+  Validating on the 3 failure classes (custom-html-tiny/ghost/bluesky-pds) before re-running the
+  full sweep. /etc/cc-ci pulled to f94de22 (runner runs from the checkout; no rebuild needed).
+
 ## Claims awaiting verification
-- **M1 — CLAIMED** (this commit). Awaiting Adversary PASS in REVIEW-canon.md.
+- **M1 — PASS** (Adversary 3bdd5d1, no VETO). M2 work in progress (not yet claimed).
 
 ## Blocked
 (none)