diff --git a/specs/adr/0004-serialized-run-groups.md b/specs/adr/0004-serialized-run-groups.md
index aa7b909..7a23585 100644
--- a/specs/adr/0004-serialized-run-groups.md
+++ b/specs/adr/0004-serialized-run-groups.md
@@ -1,6 +1,6 @@
 # ADR-0004 — Serialized run groups: one in flight, newest waiter wins, in D1
 
-**Status:** proposed 2026-09-18
+**Status:** accepted 2026-09-18
 **Related:** `packages/runtime-cf/src/serial-queue-d1.ts` · `apps/dispatcher/src/workflow.ts` · `runs/worker-deploy.ts` · `infra/migrations/0008_serial_queue.sql` · ADR-0001 § Consequences ("No per-entity mutex")
 
 ## Context
diff --git a/specs/adr/README.md b/specs/adr/README.md
index f2dd508..04b36c7 100644
--- a/specs/adr/README.md
+++ b/specs/adr/README.md
@@ -14,4 +14,4 @@ interfaces or assume they exist.
 | [0001](./0001-cloudflare-workflows-scope.md) | proposed | How runs use Cloudflare Workflows: one instance per dispatch, hibernation reserved for bounded human decisions, entity lifecycles keep state in the system of record |
 | [0002](./0002-memory-capability.md)          | proposed | Org context is an optional, total `memory` capability with MCP-speaking adapters; runs consume, never produce                                                        |
 | [0003](./0003-no-context-relay.md)           | proposed | Context backends ingest GitHub directly; FlareDispatch builds no relay, export, or pull endpoint for them                                                            |
-| [0004](./0004-serialized-run-groups.md)      | proposed | A run may declare a serialization group: one execution in flight, newest waiter wins, never cancel the running one; state in D1                                      |
+| [0004](./0004-serialized-run-groups.md)      | accepted | A run may declare a serialization group: one execution in flight, newest waiter wins, never cancel the running one; state in D1                                      |