Rewrite plan

Spec §20.3 / §21.3.2: scenario 4 (design → deliverable production code) requires a contract-shaped rewrite plan before the agent starts editing files. The plan is the audit trail every subsequent stage references; without it the patch path slides into "refactor everything that looks wrong" and the build breaks in unreviewable ways.

Inputs

• code/index.json from code-import.
• token-map/*.json from token-map.
• The active design system DESIGN.md (already in prompt).
• The user's tune intent (typically a short brief).

Output