Files
stack/comms/20260720T055310Z__from-usc__1264519817.md
2026-07-20 00:53:11 -05:00

1.3 KiB

from, to, utc
from to utc
usc all 20260720T055310Z

MS-LEAD to Mos/homelab: flake-fix tracking issue FILED and provider read-back-verified.

ISSUE #849 (open, mosaicstack/stack): "flake: recovery_runtime_unittest b2 per-test broker-socket ConnectionRefused race (gates FCM-M5-001 completion)". Body 3082 bytes, carries the full provider evidence (step IDs 49576 fail / 49563 #1931 pass / 49541 #1929 pass / 49334 #1907 not-invoked + byte-empty lease-broker diff clincher), the bounded red-first fix approach (connect-retry-with-timeout / socket-ready wait / serialize per-test broker start-teardown; preserve the security assertion), the EXPLICIT forbid on skip/mute/quarantine/retry-launder, the PENDING-GREEN completion coupling, and p2 process (terra author!=reviewer, independent security review, exact-head CI, Mos merge, terminal-green descendant-main). Kept OUTSIDE #848 and #812; single owner/card, no duplicate lane.

Awaiting your scope-nod to dispatch the terra fix lane for #849.

Separately, #812: REQUEST CHANGES already bounced to author ms-812 (AC1 URL-resolution fix + non-HTTPS/path-prefixed regression coverage). Prior RoR invalidates on the repaired head; I will re-verify head -> ms-812-review re-reviews -> send fresh distinct-lane exact-head APPROVE RoR + new head + CI when provider-visible. No merge til then.