QUEUE rows 9-13 (#1508): process becomes data, one writer, ledger checks; AGENTS.md cadence reads QUEUE.md first

Jason: the process goes off the rails every time because the entry point is
prose. Rows 9-13 are marked required and cannot be parked.

Co-Authored-By: Claude Fable 5.1 <[email protected]>

AGENTS.md

@@ -51,9 +51,10 @@ green at every step. Not production software — a proven foundation.
 
 - **Register** your session in `docs/SESSIONS.md` — one append-only line
   (date, actor, scope, outcome). Never rewrite or remove entries.
-- **Cadence**: read `docs/plans/CURRENT.md` → execute its single next action
-  fully (implement → test → verify against acceptance criteria → commit →
-  push → close issue) → update CURRENT.md → register in SESSIONS.md.
+- **Cadence**: read `docs/plans/QUEUE.md` first; your next piece is the first
+  row you own that is briefed, in progress or in review, nothing else. Open only
+  the brief that row links to. Execute it fully (implement → test → verify against acceptance criteria → commit →
+  push → close issue) → move your QUEUE.md row → register in SESSIONS.md.
 - "next" means one action. A batch mandate ("run the queue") repeats the
   loop until green or blocked. Blocked means stop and report, never improvise.
 - Substantial work gets a Gitea issue and a BUILD-LOG phase entry
@@ -99,7 +100,8 @@ Full reference — usage, fields, exit codes, safety notes:
 
 ## Pointers (depth lives here)
 
-- `docs/plans/CURRENT.md` — THE next action (single source of "what now")
+- `docs/plans/QUEUE.md` — THE task list (one row per piece; read first)
+- `docs/plans/CURRENT.md` — narrative log behind the queue rows
 - `docs/plans/ROADMAP.md` — agreed milestone path (M16+)
 - `docs/plans/CONDUCTOR.md` — orchestration protocol and guardrails
 - `docs/plans/2026-09-02_atomic-mosaic-foundation.md` — architecture, invariants