status(rcust): disclosed SIGINT shortcut of doomed m2p overlay install burn (KeyboardInterrupt at the diagnosed converge line); m2p2 is the binding proof

JOURNAL-rcust.md

@@ -228,3 +228,24 @@ green. Guard: Failed/mixed/spinning-up/no-tasks-yet still block (unit-pinned, 7
 
 Branch fix/converged-oneshot @ be2026a, proposal in ADVERSARY-INBOX, awaiting approval per the M2
 fix-forward protocol. Unit suite 199 passed + lint PASS from the cc-ci working-tree rsync.
+
+## 2026-06-11 ~01:00Z — merge landed, queue shortened
+
+be2026a approved (REVIEW a531746, cold-verified independently) and merged as 6cabbe7; drone build
+350 green on the push head 914c166. Merged diff verified == branch diff (empty git diff be2026a..
+main for the two files). Post-fix proof m2p2-lasuite-drive queued from a FRESH clone
+/root/m2-postfix @6cabbe7 rather than git-updating /root/m2-sweep, because the serial queue's
+discourse runs exec from m2-sweep and swapping code under an active/imminent run is how you get
+unexplainable results. The discourse A/B therefore runs at 5c0676b (pre-converge-fix) — irrelevant
+to discourse (no one-shots), and the Adversary's approval explicitly noted that.
+
+Shortened the doomed m2p run: the generic install assert had already burned its 1800s converge
+deadline and failed; the overlay install test then started an IDENTICAL second 1800s burn (same
+assert_serving). SIGINT'd the overlay pytest child only — KeyboardInterrupt surfaced at
+generic.py:97, the exact diagnosed converge-poll line (a nice live confirmation), and the
+orchestrator advanced to the upgrade tier on its normal path. Teardown semantics untouched.
+Disclosed in STATUS so the log's KeyboardInterrupt is pre-explained.
+
+Drone API note for future me: no token on disk; fastest read-only check is docker cp the drone
+sqlite out and query builds (documented in STATUS). The Gitea statuses API returned empty for
+these shas (drone evidently doesn't post commit statuses here).

STATUS-rcust.md

@@ -151,6 +151,13 @@ sweep runs, not retroactively here.
      runs lasuite-drive @ffa7d585afa2 PR=1 from fresh clone /root/m2-postfix @6cabbe7 →
      CCCI_RUN_ID=m2p2-lasuite-drive, log /root/m2-proof-logs/lasuite-drive-postfix.log.
      EXPECTED **L5** (binding condition 1 of the approval).
+     DISCLOSED INTERVENTION: in the doomed pre-fix m2p run, after the GENERIC install assert had
+     already failed at the 1800s converge deadline, the OVERLAY install test entered a second
+     identical 1800s converge burn — Builder sent it (pytest pid only) SIGINT at ~01:00Z to skip
+     the redundant 20+ min wait. The log therefore shows `KeyboardInterrupt` at generic.py:97
+     (the converge poll — the exact diagnosed line). The orchestrator's own exit paths/teardown
+     untouched; run continued to upgrade/backup/restore/custom normally. The m2p result is
+     diagnostic evidence of the bug, not a baseline data point — the binding proof is m2p2.
   2. **discourse @7ae7b0f PR=2 on merged main** (exact baseline-184 invocation) → m2p-discourse;
      discriminates PR=0-artifact/race vs deterministic-at-ref. Unaffected by the one-shot issue.
   3. **discourse @7ae7b0f PR=2 on OLD main** (/root/m2-oldmain) → ab-discourse-7ae7b0f-oldmain;