plan-issuelisted

# Plan Issue Complete the SDD phases `Plan` and `Tasks` for exactly one GitHub Issue. ## Workflow 1. Accept exactly one issue number or URL. 2. Read the issue title and body, every issue comment, linked issues, linked PRs, applicable `AGENTS.md`, code, tests, documentation, and relevant history. 3. Reconstruct the canonical `Specify` and `Clarify` contract. Do not assume the newest comment automatically overrides older content. Look for explicit decisions, confirmations, and supersession. 4. If `Specify` or `Clarify` is materially incomplete, delegate to `capture-issue` or stop with an exact preparation gap. 5. Inspect the current code instead of trusting stale file lists in the issue. 6. Use `grilling` only for unresolved consequential choices. 7. Route to `domain-model`, `module-design`, `research`, `prototype`, or `dont-reinvent-the-wheel` only when their exact triggers apply. 8. Update the canonical issue with `Plan` and proportional `Tasks`. Verify that every acceptance criterion, dependency, and major risk is covered. 9. Refetch the issue before writing to avoid overwriting concurrent edits. ## Plan content Include when applicable: - chosen approach - important rejected alternatives - architecture and ownership boundaries - affected modules and responsibilities - interfaces and contracts - data and state flow - compatibility and migration concerns - accessibility, security, and failure behavior - documentation updates - dependencies and coordination - risks and reg