spec-driven-migrationlisted

# Spec-Driven Migration Replace every occurrence of a `from_pattern` with a `to_pattern` across a defined file scope, preserving the framework's dual-path (`.claude/` ↔ `src/claude/`) byte-identity, with phase-enforced classification, parallel cluster workers, and global verification. Every step uses Execute-Verify-Record to prevent token optimization bias from skipping phases. **The migration intent (from/to pattern + scope + exclusions) is the input. A clean, dual-path-byte-identical codebase + a verifiable migration report is the output. User approval gates every classification cutover and the final commit.** **If ambiguous or conflicts detected: HALT and use AskUserQuestion** --- ## Execution Model See **`.claude/rules/core/anti-skip-behavior.md`** for the canonical execution contract (expand inline; do not wait passively or offer execution options; honor every step of every phase; Self-Check violation taxonomy; Token-Optimization-Bias prohibition; governed by ADR-076). After invocation, execute Phase State Initialization immediately. --- ## Anti-Skip Enforcement Contract Enforced structurally outside LLM control, not by this prose — by the framework's deterministic gates wired for this workflow: the `devforgeai-validate` phase gates, the `settings.json`-registered `.claude/hooks/` scripts, and `.claude/hooks/phase-steps-registry.json` (ADR-076). Behavioral residue: `.claude/rules/core/anti-skip-behavior.md`. --- ## Parameter Extraction Extract parameters from