refactorsolid

# refactor Select this owning procedure for a behavior-preserving restructure, whether requested in plain language or through `/refactor`. Entry syntax is not an additional gate; the approved-surface, parity, and verification requirements below still apply. Externally observable behavior before equals after, proven rather than assumed. ## Entry boundaries - Identify both the surface and the motivation. Phase 1 owns the precise surface table and its approval; knowing a command name does not establish either. - New behavior, including a new error path, side effect, or public method beyond a Phase 3 seam, belongs to `/feature`. Incorrect existing behavior belongs to `/fix`. - An explanation-only question stays in the non-mutating question-answer path, not this editing procedure and not a required help-command detour. - Persisting an already-completed refactor belongs to the existing commit owner at [routines/commit-gate/SKILL.md](../commit-gate/SKILL.md), with its actual authorization and gates. No commit, push, or PR is implied merely by entering this refactor procedure. ## Pre-flight Read these, or STOP and surface the gap — never guess a command or a threshold: - `<project-root>/.codearbiter/CONTEXT.md` — the `stage:` frontmatter (the maturity value) and project context. - `<project-root>/.codearbiter/tech-stack.md` — the test, coverage, lint, and type-check invocations; file layout. - [includes/verification-boundary.md](../../includes/verification-boundary.md