refactor

## Sub-agent contract /contract **Skip when:** the change touches ≤3 files and no dependency ordering is required — just edit directly. Also skip when the codebase has no test coverage at all (behavioral preservation cannot be verified; ask the user to add tests first or proceed manually). --- ### Triage (inline, before dispatching any sub-agent) Parse `$ARGUMENT` to extract: - **Change type**: rename | api-migration | pattern-standardization | layer-restructure | dependency-upgrade | other - **Target symbol / path / pattern** (what is changing) - **Destination** (what it becomes) - **Scope**: default to the entire repo; narrow if `--scope` is provided If `$ARGUMENT` is ambiguous on any of the above, stop and ask exactly one question. --- ### Wave 1 — Scope enumeration (parallel, `subagent_type: "research-agent"`) Dispatch both agents simultaneously in a single response turn. **Site-finder agent** - goal: Enumerate every file and symbol that must change for the refactor to be complete and correct. - inputs: change type, target symbol/pattern, scope glob - artifacts: - `sites`: array of `{file, line_range, site_type: "definition"|"import"|"usage"|"type-ref"|"test", change_required: string}` - `dependency_graph`: for each site, which other sites must be changed first (a site depends on its callers if it exports a symbol; a definition must be changed before its imports) - `site_count`: integer - `confidence`: low | medium | high - `coverage_gaps`: what the age...