M1(verified): bump SPEC §23 + README to 'shipped' (live smoke passed)

README.md

@@ -7,12 +7,13 @@ normalizes them, resolves recipients via `companies` → `groups` →
 Telegram, SMS, email, voice, Slack, MS Teams, and arbitrary outbound
 webhooks.
 
-> **Status**: M0 + M1 code-complete 2026-06-13. M0 is the single-host
+> **Status**: M0 + M1 **shipped** 2026-06-13. M0 is the single-host
 > docker-compose stack + 4 Go services + loadgen-http + alert schema.
 > M1 is the end-to-end: signed webhook → broker → router → deliverd
-> → fakefcmd. See `M0_VERIFICATION.md` and `M1_VERIFICATION.md`
-> for the smoke tests. Spec is in `SPEC.md`, diagrams in
-> `ARCHITECTURE.md`, build log in `PROMPT.md`.
+> → fakefcmd (live-verified, 1530 deliveries in the loadgen burst,
+> 0 failures). See `M0_VERIFICATION.md`, `M1_VERIFICATION.md`, and
+> `M1_SMOKE_LOG.md` for the smoke tests. Spec is in `SPEC.md`,
+> diagrams in `ARCHITECTURE.md`, build log in `PROMPT.md`.
 
 ## v1 in one paragraph
 

SPEC.md

@@ -883,7 +883,7 @@ ingestd_rejection_latency_seconds_bucket{transport,reason} histogram
 | # | milestone | exit criterion |
 |---|---|---|
 | M0 | Skeleton + docker-compose up | Postgres + NATS + Redis up, all 4 services start, /health green | **✅ shipped 2026-06-13** |
-| M1 | HTTP POST ingest end-to-end | send a signed webhook → FCM test push to a fake device; layers 1, 3, 4, 5 in | **✅ code complete 2026-06-13** (awaiting live smoke test) |
+| M1 | HTTP POST ingest end-to-end | send a signed webhook → FCM test push to a fake device; layers 1, 3, 4, 5 in | **✅ shipped 2026-06-13** (live smoke test all 9 steps green; see `M1_SMOKE_LOG.md`) |
 | M2 | Recipient resolution | per-source `allowed_targets` honored, subscriptions applied |
 | M3 | Telegram delivery + bot commands | user can `/subscribe` and receive an alert via Telegram |
 | M4 | MQTT ingest | EMQX up, QoS 1, per-company topic ACLs |