namht-plan-reviewlisted

# namht-plan-review — multi-lens critique of a plan (catch bad plans early) A plan is the cheapest place to fix a mistake. Review the plan (from `/namht-plan`, `/namht-discover`, or pasted) before code. ## Input The plan / user stories (pasted, or a file under `namht-sessions/`). Identify the feature + the modules/entities it targets. Ground in KB (`13-business-rules`, `16-architecture-patterns`, `10-core-flows`) and by tracing callers (blast radius of the proposed changes). ## Lenses (score each: ✅ ok / ⚠️ concern / ❌ blocker) 1. **Product** — is this the *right* thing? Is there a simpler version that delivers most value? Scope creep? Does it match the success metric? Anything that should be cut or deferred? 2. **Architecture / Eng** — does it follow the documented pattern & layer rules (`16-architecture-patterns`)? Blast radius (who else is affected — grep callers)? Migrations / breaking changes handled? Any risky shortcut? 3. **Risk / QA** — what existing flows could break (regression)? Edge cases, error paths, concurrency, permissions, data states the plan ignores? Is it testable? 4. **DevEx / Maintainability** — complexity added, duplication, naming, "will the next dev understand this?", premature abstraction (YAGNI). 5. **Reuse & Rollout** (when the plan came from `/namht-build`) — check its **Reuse Report**: for every row marked `new`, does the justification name real searches, and can you find an existing candidate it missed (helper, service, D