architecture-reviewlisted

# Architecture review — find and explore deepening opportunities Surface architectural friction and propose **deepening opportunities** — refactors that turn shallow modules into deep ones. The aim is testability and navigability. This skill is **self-executed by the active primary**: it reads the codebase directly and produces its own report. It composes with, and does not replace, the routed skills: for an independent cross-family read on the top candidates, route them through `architect` afterward. ## Design vocabulary Use these terms exactly in every suggestion — do not drift into "component," "service," "API," or "boundary": - **Module** — anything with an interface and an implementation; deliberately scale-agnostic (a function, class, package, or tier-spanning slice). - **Interface** — everything a caller must know to use the module correctly: types, invariants, ordering constraints, error modes, configuration, performance characteristics. - **Implementation** — what is inside the module. - **Depth** — leverage at the interface: how much behavior a caller or test can exercise per unit of interface learned. **Deep** = small interface, large behavior; **shallow** = interface nearly as complex as the implementation. - **Seam** — a place where behavior can be altered without editing in that place; where the interface lives. Placing the seam is its own decision. - **Adapter** — a concrete thing satisfying an interface at a seam (a role, not a substance). On