Add /adjudicate command: debate low-priority backlog to a verdict

Parked P2/P3 technical items accumulate faster than I can judge their
necessity. /adjudicate runs a grounded per-item debate (investigator →
build/drop advocates → judge) over a repo's ROADMAP and routes each to
DROP / DO / ESCALATE, so I ratify decisions instead of researching them.

Recommend-only in v1; verdict autonomy is gated by blast radius, not
priority. ROADMAP-only input — nudges /triage rather than reading the
raw inbox.

AGENTS.md

@@ -17,7 +17,8 @@ The global layer lives here and is wired into `~/.claude` by **directory symlink
 file added under `adapters/` is live immediately — no per-file linking:
 
 - `~/.claude/commands` → `adapters/claude/commands/` — global slash commands (`/retrofit`,
-  `/handoff`, `/full-eval`, `/capture`, `/triage`, `/roundup`, `/new-project`, `/design`).
+  `/handoff`, `/full-eval`, `/capture`, `/triage`, `/roundup`, `/new-project`, `/design`,
+  `/adjudicate`).
 - `~/.claude/agents` → `adapters/claude/agents/` — global subagents (reviewer, evaluator,
   security-auditor, doc-auditor, exerciser, researcher, janitor, portability-checker,
   start9-spec-checker, design-checker, onboarding-tester).
@@ -88,9 +89,18 @@ should carry this so any vendor's agent surfaces pending items at session start:
 ## Current state
 
 - **Fleet built and live** — commands `/capture /triage /roundup /new-project /handoff /retrofit
-  /full-eval /design`; subagents incl. `design-checker` + `onboarding-tester` (substance in
-  `guides/`, thin wrappers in `adapters/claude/`, symlinked into `~/.claude`). Dogfoods its own
-  standard. Latest `/roundup`: `STATUS.md` 2026-06-16.
+  /full-eval /design /adjudicate`; subagents incl. `design-checker` + `onboarding-tester`
+  (substance in `guides/`, thin wrappers in `adapters/claude/`, symlinked into `~/.claude`).
+  Dogfoods its own standard. Latest `/roundup`: `STATUS.md` 2026-06-16.
+- **`/adjudicate` built this session (ROADMAP item 10), live.** Debates each parked P2/P3 backlog
+  item on a repo's ROADMAP to a verdict so the owner ratifies instead of researching: per item,
+  investigator (grounds it in the code + classifies blast radius) → build- ∥ drop-advocate → judge
+  (rubric = `how-i-work.md` + repo `AGENTS.md`, biased to DROP on ties). Verdicts: **DROP** (auto,
+  ratified in one batch), **DO** (low blast radius → annotated plan, recommend-only), **ESCALATE**
+  (HIGH blast radius / low confidence → balanced brief for the owner). Autonomy gated by blast
+  radius, not priority; ROADMAP-only (nudges `/triage` first, never reads raw inbox). **v1 is
+  recommend-only** — never executes; v2 (narrow auto-execution of the safe DO class) deferred until
+  trust is built.
 - **`onboarding-tester` built this session (ROADMAP item 9), live.** Docs-only adopter agent: walks
   a product's published docs as a literal newcomer (never reading source), reports doc gaps, and on
   a fully clean run emits a publishable "all it took was X, Y, Z" walkthrough. First target: keysat