status(rcust): m2p-lasuite-drive WILL land L0 — second P2b regression (completed one-shot 0/1 vs services_converged) root-caused live; fix on branch be2026a awaiting approval

STATUS-rcust.md

@@ -127,9 +127,23 @@ sweep runs, not retroactively here.
 - M2.3 in-flight proof runs (serial queue /root/m2-proof.sh + /root/m2-proof2.sh, logs
   /root/m2-proof-logs/, driver /root/m2-proof-logs/driver.log):
   1. **lasuite-drive @baseline ref ffa7d585afa2 PR=1 on merged main @5c0676b** (post-fix-forward
-     1357544) → run id m2p-lasuite-drive; EXPECTED L5 (the Adversary approval condition).
+     1357544) → run id m2p-lasuite-drive: **WILL LAND L0 — second P2b regression found via this
+     run, root-caused LIVE.** The 1357544 best-effort path WORKED (`!!` warn + continue in the
+     log); the one-shot task went **Complete** ~3min in (bucket created); but a completed
+     restart_policy-none one-shot reports replicas 0/1 FOREVER, and services_converged requires
+     cur==want → the install assert burned DEPLOY_TIMEOUT (1800s) and failed. Old world never saw
+     this: setup_custom_tests.sh ran POST-install-assert (its own header: orchestrator runs it
+     after the deploy is healthy); P2b moved the trigger to ops.py pre_install = PRE-assert.
+     Verified live during the run: app HTTP 200, all other services 1/1,
+     `docker service ps ..._minio-createbuckets` = Complete, pytest in converge loop 27+ min.
+     **Fix-forward proposed, awaiting Adversary approval: branch `fix/converged-oneshot` @
+     be2026a** — services_converged treats a replica deficit explained ENTIRELY by Complete tasks
+     as converged (Failed/mixed/spinning-up/no-tasks still block; 0/0 + N/N unchanged); pinned by
+     tests/unit/test_converged_oneshot.py (7 cases). Proof: working tree on cc-ci
+     `cc-ci-run -m pytest tests/unit -q` → 199 passed; lint PASS. Post-approval: merge + re-run
+     this proof (expect L5).
   2. **discourse @7ae7b0f PR=2 on merged main** (exact baseline-184 invocation) → m2p-discourse;
-     discriminates PR=0-artifact/race vs deterministic-at-ref.
+     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.
 - M2.4 spot-greps (customizations actually executed — log evidence in /root/m2-logs/):