status(lvl5): ## DONE — M1 (cfc87fd) + M2 (13cad1f) both PASS, no VETO; L5 lint rung + de-capped levels live end-to-end; cleanup complete

BACKLOG-lvl5.md

@@ -13,7 +13,7 @@
 - [x] B9 — gate M1: claim (branch w/ P1+P2; clean tree; cold-verifiable).
 - [x] B10 (P3) lint sweep over ALL enrolled recipes (scratch clones — never touch ~/.abra/recipes during builds); matrix here (pass/fail + rule hits); mechanical fixes → mirror PRs (never push main/never merge); rest → DEFERRED.md.
 - [x] B11 (P4) real-CI proofs: ≥1 genuine L5; ≥1 lint-blocked L4 (synth branch ok); ≥1 N/A-skip climb; 2× drone !testme; canary suite at re-derived designed levels; 1 synthesized unver-blocks run; before/after level table for ALL enrolled recipes; card/dashboard PNG/SVG visually verified.
-- [ ] B12 — gate M2: claim; then ## DONE after fresh PASS.
+- [x] B12 — gate M2: claim; then ## DONE after fresh PASS.
 
 ## Adversary findings
 

JOURNAL-lvl5.md

@@ -107,3 +107,10 @@
   completeness. Surfaced to Adversary in the M2 claim notes; not fixing inside this phase.
 - M2 claimed in STATUS-lvl5 with the full evidence table (runs 398/399/405/406/407/413/415/416 +
   lvl5-unver-demo). B11 ticked.
+
+## 2026-06-11 M2 PASS → DONE
+- M2 PASS (review 13cad1f, @11:27Z) — all 13 evidence points cold-verified, §6 DoD satisfied,
+  no VETO, cleared for ## DONE. Both gates passed today (M1 cfc87fd, M2 13cad1f); no standing VETO.
+- Cleanup: PR custom-html#4 closed + branch lvl5-lintdemo deleted (204). WC5 stage-completeness
+  observation filed to machine-docs/DEFERRED.md (operator decision; Adversary concurs not a finding).
+- Phase complete: L5 lint rung + de-capped level semantics live end-to-end.

STATUS-lvl5.md

@@ -1,9 +1,14 @@
 # STATUS — Phase lvl5 (L5 lint rung + de-cap)
 
-Phase: lvl5 — M1 PASS (cfc87fd); P3+P4 complete
-Gate: **M2 CLAIMED, awaiting Adversary** (claimed 2026-06-11)
-In flight: parked at M2 (no unblocked items remain)
-Blockers: none
+## DONE
+
+Phase complete 2026-06-11: M1 PASS (cfc87fd) + M2 PASS (13cad1f), both <24h, no VETO.
+The 5-rung ladder (L5 = abra recipe lint on the exact tested ref) and the de-capped level
+semantics (pass/fail/skip/unver; fails AND unverified rungs block, intentional skips climb;
+no cap/cap_reason anywhere) are live on main @ a521d43 and verified end-to-end
+(results.json schema 2 → card → dashboard → badge → PR comment, drone path included).
+Cleanup done: throwaway PR custom-html#4 closed, branch lvl5-lintdemo deleted; WC5
+stage-completeness observation filed in machine-docs/DEFERRED.md.
 
 ## M2 claim — proven in real CI
 

machine-docs/DEFERRED.md

@@ -360,3 +360,13 @@ before the build is called done) — but does **not** force closure.
   Evidence: /tmp/mumble-probe{2,3,4}.out + /tmp/mumble-orch{4,5}.log on cc-ci (90s DOM/console/
   network observation; websockify reachable, /ws & /websocket 404 from websockify itself);
   /var/lib/cc-ci-runs/shot-proof-mumble/screenshot.png (L4 run, loader frame).
+
+## WC5 promote-on-green-cold ignores stage completeness (filed 2026-06-11, Builder, phase lvl5)
+
+Observed during the lvl5 unver-blocks proof: a GREEN hand-run with `STAGES=install,upgrade,custom`
+(backup/restore excluded) on latest still advanced custom-html's warm canonical —
+`should_promote_canonical` checks green+cold+latest but not that ALL stages ran. Pre-existing
+behavior (not introduced or worsened by lvl5; Adversary concurs it is not a finding). Only
+reachable via the operator/dev STAGES escape — production drone runs always run all stages.
+**Needed from operator:** decide whether promote should additionally require the full stage set
+(one-line guard in `should_promote_canonical`), or whether dev hand-runs promoting is acceptable.