status(rcust): discourse A/B CLOSED — old==new byte-identical upgrade-HC1 at baseline ref+invocation (harness-neutral, env drift since 06-05; branch-tip/tag/abra-pin drift eliminated); m2p2 lasuite-drive binding proof started

STATUS-rcust.md

@@ -158,10 +158,25 @@ sweep runs, not retroactively here.
      (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;
-     completes the same-ref A/B the upgrade-HC1 mode is missing.
+  2. **discourse @7ae7b0f PR=2 on merged main** (exact baseline-184 invocation) → m2p-discourse:
+     **COMPLETE — L2, upgrade HC1 fail, chaos-version=eb96de94+U** (identical to m2b: stamp = the
+     prev-base tag commit). Deterministic at this ref on new main; NOT a PR=0 artifact, NOT a race.
+     install/backup/restore/custom all pass.
+  3. **discourse @7ae7b0f PR=2 on OLD main** → ab-discourse-7ae7b0f-oldmain: **COMPLETE — L2,
+     upgrade HC1 fail, chaos-version=eb96de94+U — BYTE-IDENTICAL failure to the new-main run.**
+     **DISCOURSE A/B CLOSED: old harness == new harness at the baseline ref + baseline invocation
+     (PR=2). The upgrade-HC1 mode is HARNESS-NEUTRAL — not an rcust regression.** Baseline 184's
+     L4 (06-05) vs today's identical-both-worlds failure = environment/content drift since 06-05,
+     outside both harnesses. Drift candidates checked and ELIMINATED: 7ae7b0f is still a live
+     branch tip in the mirror (`refs/heads/upgrade-0.8.0+3.5.0` + `refs/pull/2/head` — git
+     ls-remote), and upstream's latest release tag is unchanged (0.7.0+3.3.1 = eb96de94, no new
+     tag since 06-05). flake.lock (abra pin) identical in both worlds. HC1 firing rather than
+     false-greening is the guard working as designed.
+     Cold-verify: results.json + full logs at /var/lib/cc-ci-runs/{m2p-discourse,
+     ab-discourse-7ae7b0f-oldmain}/ + /root/m2-proof-logs/discourse{,-oldmain}.log.
+  4. **lasuite-drive @ffa7d585afa2 PR=1 on merged main @6cabbe7 (post-converge-fix)** →
+     m2p2-lasuite-drive: STARTED 00:48:58Z (log /root/m2-proof-logs/lasuite-drive-postfix.log).
+     EXPECTED **L5** (binding approval condition 1).
 - M2.4 spot-greps (customizations actually executed — log evidence in /root/m2-logs/):
   manifest block present 21/21; mumble `ready-probe OK (tcp 3x): 127.0.0.1:64738`; ghost+discourse
   `ccci-overlay: provided compose.ccci.yml ... auto-chaos` (P2a first-class path live);