review

Check a legacy feature (has `data/state/` or `services/main-service/`) against the legacy rules; don't flag the layout itself. Read the files under the given path and assess them against the relevant `features/` rules (each layer's rule and the cross-cutting rules — `namespace`, `data-modelling`, `type-casts`, `cohesion`, …): - **Correctness** — does it typecheck and follow the layer's required shape? - **Adherence** — single public export per file, naming, per-file scope flags (`Scope`), `satisfies` targets, barrels, the layer dependency order (no runtime import of `spec/`), store-layer typing, etc. - **Generality** — no leaked type identities; follows the cross-cutting patterns. Report either **OPTIMAL**, or a short list of issues. Tag each issue with where the root-cause fix belongs: - `code` — a one-off slip in the generated files (guidance is fine), - `skill` — the phase skill's instructions are unclear, wrong, or incomplete, - `rule` — a referenced rule is unclear, wrong, or missing guidance. Do not edit anything — assessment only.