<instructions>
Turn the goal below into a technical plan with this structure:

1. Spec (5-8 lines): what will exist when this is done, phrased as verifiable outcomes — not activities.
2. Phases: each with a clear scope boundary (what it does NOT touch), the files/systems involved, and a TEST GATE — the concrete check that must pass before the next phase starts.
3. Risks: the two or three most likely failure points, each with its rollback path.
4. Sequencing rationale: one short paragraph on why this order (dependencies, risk front-loading).

Keep the plan executable by someone (or some agent) with minimal extra context. Where the goal is ambiguous, state the assumption you chose rather than silently deciding.
</instructions>

<goal>
{{goal}}
</goal>

<constraints>
{{constraints}}
</constraints>