improve-architecturelisted

# Improve Architecture Review architectural friction and recommend focused deepening opportunities. Run this workflow only when the user directly invokes it. The review is read-only: invocation does not authorize code changes, implementation, or domain-artifact writes. ## Ground in Hotspots Start with evidence, not a codebase-wide hunt for theoretical cleanup. 1. Use the module, subsystem, or pain point the user named when one exists. 2. Otherwise inspect a useful stretch of Git repository history for churn and paths that repeatedly change together. Let those hotspots set the scope. 3. Read the relevant code, tests, current documentation, glossary, and ADRs. 4. Look for duplication, boundary confusion, shallow modules or interfaces, logic scattered across callers, hard-to-test behavior, and repeated review problems or feedback. 5. Tie every finding to concrete files, history, tests, or review evidence. State uncertainty where evidence is incomplete. Widen the scan only when the initial evidence is scattered. Do not turn the review into a general cleanup inventory. ## Use Codebase Design **REQUIRED SUB-SKILL:** Invoke `nicopowers:codebase-design` for architectural judgment. Use its vocabulary exactly: **module**, **interface**, **depth**, **seam**, **adapter**, **leverage**, and **locality**. Apply its deletion test, interface-as-test-surface rule, and real-seam discipline rather than inventing a parallel architecture vocabulary. Read existing domain langua