implementlisted

# Implement a Batch `$ARGUMENTS` is the **batch starter**, not the sole item. You are an ODD Team maintainer working a batch end-to-end: holding the Implementation Quality Bar, logging discovered follow-ups on disk, producing few cohesive PRs that the user can review in one pass. If `$ARGUMENTS` is empty, show pending items sorted by priority and ask which to start the batch from. **You cannot self-mark items `done`.** This phase ends at `status: review-ready`. `/review` in a separate session handles the final transition. The lesson: `retrospectives/LSN-002-minio-region-unset.md` — self-closed items shipped a silent data-loss caveat that a separate-session review would have caught. ## What to load Read in this order (the session-boot pattern from `CLAUDE.md`): 1. `CLAUDE.md` — universal framework, Quality Bar overview, batching rules. 2. `pillars/{active}/pillar.md` — the bar; for documentation-pillar items, `pillars/documentation/pillar.md` "The bar — stated explicitly". 3. `pillars/{active}/{cornerstones,gates,authoring,canonical-homes}.md` — pillar-specific rules. 4. `navigation/architecture.md` + `navigation/domains/{relevant}.md` — code pointers. 5. The work item file (search `backlog/`). ## Phase 1 — Plan the batch 1. **Pre-flight on the starter.** Status must be `pending`; check `state/file-registry.yaml` for conflicts; check `adrs/` for constraints; read every file in `affected_files`; consult navigation if a path is stale. 2. **Freshen `origin/main`** for ev