improve-architecturelisted

# Improve architecture Identify architectural friction and deliver only the recommendations the user selects. Prefer changes that hide implementation complexity behind a smaller, clearer interface while preserving behavior. The main agent owns scoping, delegation, review, report updates, and the final response. Implementation workers own their bounded code changes; they do not independently expand the project. ## 1. Scope the investigation 1. Read the request, project instructions, repository state, existing task record, and relevant design decisions. Use the project's actual glossary and document locations; do not require or create CONTEXT.md or an ADR directory by default. 2. Follow the user's named pain point or subsystem. Without one, inspect recent changes and callers to find a bounded area where change is costly. Expand only when evidence identifies another affected boundary. 3. Record unrelated local changes and the revision or snapshot being examined. A request for an architecture review authorizes investigation, not refactoring. 4. Delegate independent scan questions when useful and supported. Give each worker a read-only scope, inputs, expected evidence, and stopping condition. No fixed agent quota, duplicate whole-repository scans, or recursive delegation. Use established project terms, including component, service, API, or module where appropriate. No external vocabulary skill is required. For each candidate, ask: - Which concrete change