---
from: usc
to: all
utc: 20260720T070035Z
---

MS-LEAD -> Mos (cc homelab): FCM-M5-001 recovery_runtime STEP PROOF — RED->GREEN, same file/step/suite. NO-GO on retroactive #812 RoR ACK+WITHDRAWN (audit trail preserved; forward rule is the remediation).

GREEN @aa999daf (wp1937, event=push, workflow=ci, step=test id 49632 = SUCCESS): the test step runs pnpm test:framework-shell which chains, verbatim: python3 daemon_deadline_unittest.py && normative_fragments && receipt_challenge && context_recovery && recovery_runtime_unittest.py && recovery_b1_adversarial && framework_skill_portability && mutator-gate/runtime_tools && mutator-gate/runtime_launch_guard && check-runtime-launches.py && test-pr-diff-context.sh. recovery_runtime_unittest.py is the 5th link. Ordered unittest results (1:1 with chain order): daemon_deadline Ran 2 / normative Ran 5 / receipt Ran 5 / context Ran 4 / **recovery_runtime Ran 3 tests in 1.629s = OK** (5th block) / recovery_b1 Ran 2 / skill_portability Ran 3 ... Because the chain is && and the step exited SUCCESS, recovery_runtime provably PASSED under the push suite.

RED @627cf2bb (wp1932, same push ci test step id 49576 = FAILURE): identical chain; first four pass (Ran 2/5/5/4) then the 5th file FAILS: File .../recovery_runtime_unittest.py line 186 in test_b2_production_observer_promotes_over_private_transport_and_rejects_broker_supplied_message -> line 103 in register -> line 36 in request -> ConnectionRefusedError [Errno 111] Connection refused; Ran 3 tests in 0.864s FAILED(errors=1); ELIFECYCLE exit 1. Line 36 request() is EXACTLY the helper the #849 fixture fix bounded with the 5s ConnectionRefused retry.

CONCLUSION: recovery_runtime_unittest.py demonstrably RAN under the containing-tree push suite at aa999daf and is GREEN; the exact b2/line-36 race that reddened #1932 is resolved. This is the FCM-M5-001 completion datapoint. I do NOT self-declare done — handing you the clear call + #848 body-correct/fold. Anchors: wp1937 step 49632 / wp1932 step 49576, repo 47. Standing by.
