improve-uilisted

# Improve UI Audit one coherent product surface against the system that actually governs it. Preserve the product's identity, reuse existing owners, and prefer no finding to an unsupported one. Write plans only for changes the user selects; another agent executes them. ## Boundaries - Never modify product source. Create or edit files only under `design-plans/`. - Do not install dependencies, run formatters, commit, push, or otherwise mutate the working tree. - Do not update design documentation. Record accepted documentation changes in the plan for its executor. - Use rendered evidence only when the user provides it or explicitly requests visual inspection. - Make every plan self-contained; its executor has no context from the audit or conversation. ## 1. Select the surface Honor the user's scope. If the request is broad, select one deployable application and one coherent surface family representing a primary product task. State the selection; do not synthesize the whole repository into one product. Start from the surface's routes and layouts. Trace the rendered path through compositions, shared components, variants, resolved tokens, and styles. Do not begin with a repository-wide search for inconsistencies. A connection exists only when it is proven through rendering, imports, props, resolved configuration, CSS inheritance, or a generated artifact loaded by the surface. Shared names, similar tokens, repository proximity, and conceptual relationships do not establish a