refactor

# Refactor — one structural experiment Refactor changes structure while preserving observable behavior. It performs one caller-selected transformation and reports the result. ## Procedure 1. Name the preserved behavior and the focused acceptance surface. 2. Record an honest baseline, including any reproducible ambient failures. 3. Apply one bounded transformation: extract, rename, inline, simplify, encapsulate, move, or delete dead code. 4. Run the focused check and the smallest package-level regression check justified by the changed surface. 5. Return the diff summary, commands, results, and behavior not checked. Do not combine a newly discovered behavior fix with the structural change. A red result is evidence for the caller; this skill does not revert, narrow, retry, commit, validate, or route subsequent work automatically. ## Seam experiments before commitment When the transformation needs a seam — an extraction boundary, interface, or module split — and more than one candidate seam exists, probe before you cut. Run the probe in disposable isolation (a scratch branch, worktree, or copied tree the caller's policy allows): rough in the seam, see what it forces — signature churn, import cycles, test rewrites — then discard the probe and keep only the knowledge. Stop condition: at most two probes; if the second candidate seam also fights back, report both findings to the caller instead of trying a third. Cutting the first imaginable seam directly into the working ...