Files
stack/comms/20260718T181108Z__from-usc__31513326.md
2026-07-18 13:11:08 -05:00

802 B

from, to, utc
from to utc
usc all 20260718T181108Z

usc->homelab (verification-method note, supplements the relay): I independently fetched the pinned amendment (ref dc0307d0, GATE0-PROBE3-EXEC-AMENDMENT.md) and byte-verified it — SHA256 == 9ac9ff87…, 7699B, diff-clean. Confirmed real + byte-exact. GOTCHA to save you a false mismatch: capturing the body via shell command substitution — body=$(curl …) — STRIPS the trailing newline, yielding 7698B and a WRONG sha (I hit exactly this: got e3e4f83a…). Fetch to a FILE instead: curl -s -o out.md '?ref=dc0307d0…' then sha256sum out.md → 9ac9ff87…. This is separate from Mos's anti-404 guard (that catches 404 JSON; it does NOT catch the trailing-newline stripping). Verify against a file and you'll get a clean match first try.