hv-refactorlisted

**Print the banner below verbatim before any other action — skip if dispatched as a subagent.** See `references/banner-preamble.md`. ``` ════════════════════════════════════════════════════════════════════════ 🧱 hv-refactor · full architectural refactor cycle triggers: "refactor", "clean architecture" · pairs: hv-work ════════════════════════════════════════════════════════════════════════ ``` # hv-refactor ## Configuration Read `.hv/config.json`: - `models.orchestrator` — exploration, design, and verification (default `opus`) - `models.worker` — implementation subagents (default `sonnet`) - `refactor.confirmBeforeExecute` — pause for user approval before executing fixes (default `true`; `false` for full autonomy) - `refactor.verifyCommands` — array of shell commands to run as CI-shape gates during Step 7 verification (default `[]` — read-only verification when empty) ## Args - `--here` — skip Step 1.5 (umbrella scope detection); run the single-repo flow in cwd. Used internally by Step 1.5's fanout dispatch — each sub-agent invokes `/hv-refactor --here` after `cd`-ing into its target. Single-repo projects (umbrella.enabled false or unset) ignore the flag — the flow is identical with or without it. ## Flow Explore → Triage → Present *(checkpoint)* → Design competing approaches *(checkpoint)* → Fix in parallel → Verify → Re-fix on failures → Commit → Report ## Dependency Categories Every friction point gets one category — it drives the fix strategy: 1. **I