zuvo:refactor
Refactor the requested symbols while preserving their observed behavior. Resolve
../../shared/includes/execution-policy.md and ../../shared/includes/evidence-reuse.md once.
Follow the user's current authorization, project verification rules and behavior scope.
Argument Parsing
| Argument | Action |
|---|---|
<file(s)> |
Analyze and refactor this scope |
continue |
Resume the selected contract at its recorded phase |
batch <file> |
Load batch handling in references/completion.md and ../../shared/includes/refactor-reference.md |
no-commit |
Finish verification; retain uncommitted work and report its location |
| Other documented flags | Resolve the full argument table in references/bootstrap.md |
Mandatory File Loading
Load only the current phase reference below. Read its required includes when that phase needs
them; use the realpath/hash/context-generation receipt protocol in evidence-reuse.md. After
compaction reload current requirements; a persistent file ledger is not retained context.
Do not concatenate every phase at entry. Missing optional enrichment is a named degradation;
missing mandatory safety definitions blocks the dependent assessment.
Phase routing
| Phase / contract boundary | Read on entry | Required outcome |
|---|---|---|
| 0: discovery | references/bootstrap.md |
Current worktree, capabilities, gate install, scope and refactor type |
| 1: plan | references/planning.md |
Callers, duplication, CQ baseline, behavior/symbol scope and contract |
| 2: characterize | references/characterization.md |
Every moved unit exercised on pre-change code; use ../../shared/includes/regression-fence.md |
| 3: transform | references/transformation.md |
Planned move, targeted verification, independent CQ audit under policy |
| 3: review | references/review.md |
Actual adversarial review of formatted final inputs; finding dispositions |
| 3.5–3.6: fix/audit | references/remediation.md |
Authorized fixes with linked red/green runs; test-quality substage with parent evidence |
| 4: completion | references/completion.md |
Shared verifier, content-keyed proof, required telemetry and concise result |
Definition of Done
For preserve-behavior CQ and finding disposition, read references/change-assessment.md.
Characterization, CQ audit, adversarial review and remediation remain mandatory. Keep
provider requirements unchanged; size alone does not waive a safety gate. An audit that ran
inline is labeled with its actual independence. Under preserve_behavior, fix introduced
regressions and report unrelated existing risks with their original severity. Authorized existing
bugfixes require demonstrated red/green tests; green characterization rechecks are different proof.
Create new v6 contracts using ../../shared/includes/refactor-reference.md; preserve v3–v5
records on resume. Format before the final snapshot and review. Reuse completed test, mutation
and review evidence only for verified matching inputs and scope; never treat pending runs as PASS.
Stage explicit touched paths, not git add -u. Commits follow session policy and do not replace
quality completion. Full repository checks required before push remain required.
Completion Gate Check
~/.zuvo/refactor-contract --contract <this-run-contract.json> check
Use the real exit status. This calls the hook predicates; do not recreate their shell/JSON logic.
The completion phase records the CQ matrix, finding ledger and receipts in artifacts and invokes
../../shared/includes/run-logger.md with ../../shared/includes/retrospective.md once per run.
REFACTOR COMPLETE
Human result: outcome, actual checks, unresolved risks, readiness to publish, commit and file links.
The full formal receipt belongs in the report. no-commit reports the exact worktree and diff.
Never claim COMPLETE over a pending check or critical unresolved requirement.