refine

Run the refine checkpoint after tests pass. It reviews only the feature branch's changed code, filters every proposal against the charter and ACs/specs contract, re-runs both test streams after applying changes, and reverts any proposal that fails.

It dispatches three parallel review subagents covering reuse, quality, and efficiency over the changed code, consolidates findings, filters them against the project charter, lets the human pick proposals, applies them, and emits a handoff to risk verification.

Consumer-facing changes get a graceful path: a deprecation-marked forwarding shim plus a migration note, with the new shape introduced alongside the old. Internal-only changes can be applied directly.

Do not use it to change behavior (use feature-edit), for risk analysis (use crap-analyzer), or on code that is not yet implemented and green. It also requires the prior checkpoint to be complete before starting.

The deterministic duplicate scan is optional. If the backend tool is unavailable, skipped, or errors, the Reuse subagent proceeds with its own LLM-based judgment and the status is surfaced in its prompt.