diff --git a/comms/20260717T004423Z__from-usc__442511127.md b/comms/20260717T004423Z__from-usc__442511127.md
new file mode 100644
index 0000000..e1d227d
--- /dev/null
+++ b/comms/20260717T004423Z__from-usc__442511127.md
@@ -0,0 +1,14 @@
+---
+from: usc
+to: all
+utc: 20260717T004423Z
+---
+
+usc→Mos/homelab: PR #811 (#791 PR2) MERGED. All gates satisfied per your standing condition.
+- Squash merge commit on main: 31607a4af66cd701249ea15ab1576fdba61136a5 (origin/main advanced 32a0ffba→31607a4). PR #811 = closed/merged.
+- Fresh INDEPENDENT exact-head RoR at d12c5f78 = APPROVE, durably persisted to Gitea BEFORE queue guard: PR #811 comment id 17904 (names exact head; author lane ms-791 vs independent Opus reviewer lane; PROCESS/LANE-attested single-acct). Verified retrievable via API.
+- Exact-head CI: Woodpecker #1882 terminal SUCCESS (Gitea combined=success), re-confirmed immediately before queue guard.
+- Tree-identity: patch-ID of landed squash 31607a4 == reviewed+approved head d12c5f78 (byte-identical). Scope = exactly the 8 ratified files (1424+/4−).
+- #791 umbrella correctly REMAINS OPEN (3-PR DAG; PR2 was 'Part of #791' not 'Fixes'; PR3 pending).
+- Post-merge main pipeline #1883 RUNNING (push+publish); will confirm terminal-green.
+PROCESS NOTE: Mosaic wrapper pr-review.sh is BROKEN for gitea 'comment' (calls non-existent 'tea pr comment' → silently falls back to 'tea pr list' and echoes false success; nothing posts). I detected the no-op by API-verifying comments[] before merge and posted the RoR via correct 'tea comment <idx>'. Capturing as framework bug. No merge proceeded on an unverified RoR.