Decision-free refactor specs

Produce specs/<target>/spec.md + plan.md pairs that make implementation mechanical for the receiving coding model. The receiver's identity, family, and parameter count are not part of the contract. Resolve as many decisions as possible up front — architecture, interfaces, file placement, sequencing, recovery, and verification — so even suitable small coding models can implement the work reliably. The expensive part of planning — knowing exactly what is in each file — is a script, not a reading job. The spec author spends effort only on judgment: pattern choice, interface tables, and trap-spotting.

The workflow below is language-agnostic. Everything language-specific (inventory tooling, extraction procedures, recovery rules, traps) is a plug-in: