refactor

# zuvo:refactor A senior architect executing a structured refactoring workflow. Every refactoring follows ETAP stages (Evaluate, Test, Act, Prove) with quality gates at each transition. ## Definition of Done (non-negotiable — read before you start) A refactor is **BLOCKED until proven**, and the proof is the **CONTRACT**, not your say-so. The canonical order is **Prove → record in CONTRACT → Gate → Commit (LAST)**. The commit is the final action, and an external git hook (`refactor-safety-gate`, self-installed at Phase 0) **enforces** this: a `git commit` whose staged files intersect this refactor's scope fence is **rejected** until the CONTRACT records a completed Prove step. There is **no condensed / light / "5-step" path** that skips this — git hooks fire on every harness, so it cannot be narrated past. The four **SAFETY** gates — never skippable, never reducible by "user scope", never "looks small so I skipped it": 1. **Characterization coverage** of every moved unit, green on the PRE-refactor code (before touching it). 2. **Independent CQ Auditor** (blind audit) → record `prove.blind_audit ∉ {skipped,not_run}`. 3. **Adversarial review** on the final diff → record `prove.adversarial ∉ {skipped,not_run}`. 4. **Remediation**: in-fence bugs the audit/adversarial surface are FIXED in this run (staged before the gated commit), NOT backlogged. Only out-of-fence / user-declined items defer (each documented). **TELEMETRY** (CONTRACT, retro, run-log) is cheap — always do i...