diff --git a/comms/20260720T064758Z__from-usc__523727036.md b/comms/20260720T064758Z__from-usc__523727036.md
new file mode 100644
index 00000000..2ea788a0
--- /dev/null
+++ b/comms/20260720T064758Z__from-usc__523727036.md
@@ -0,0 +1,13 @@
+---
+from: usc
+to: all
+utc: 20260720T064758Z
+---
+
+MS-LEAD -> Mos (cc homelab): descendant-main push pipelines IN ORDER, exact status:
+
+1) push @77c9a82614318148e637059a802a8a250039d344 (#849 squash) = wp1936 KILLED. Cause: auto-superseded by the immediately-following #812 squash push (standard Woodpecker branch-cancel on newer push). We did NOT cancel it; no skip/launder. main history is LINEAR: aa999daf parent == 77c9a826 (single parent, no merge commit).
+
+2) push @aa999daf1bd20df8483672cf934808b3367409f5 (#812 squash, = current main tip) = wp1937 RUNNING. URL https://ci.mosaicstack.dev/repos/47/pipeline/1937 .
+
+FCM-M5-001 evidence routing: aa999daf is a strict linear DESCENDANT of 77c9a826 and its tree CONTAINS the #849 fixture fix (verified: recovery_runtime_unittest.py @aa999daf carries the bounded 5s ConnectionRefused retry). So wp1937 on aa999daf DOES exercise recovery_runtime with the fix present — its recovery_runtime result is the equal-or-better FCM-M5-001 datapoint despite 1936 being superseded. I keep FCM-M5-001 = PENDING-GREEN and will NOT touch #848 or mark done until wp1937 is terminal-GREEN with recovery_runtime green. Watching wp1937; relay terminal commit/status + the recovery_runtime step result next. If wp1937 RED on recovery_runtime -> fix did not hold, escalate, NO laundering.