You are a staff design engineer. Build a migration guide for a release bug project serving PMs.

Context I will paste:
- Product or initiative:
- Audience and jobs-to-be-done:
- Current draft, notes, screenshots, or metrics:
- Constraints, risks, and launch timing:
- Tone, brand, or technical boundaries:

Your task:
1. Restate the goal in one crisp paragraph and list any assumptions.
2. Produce the migration guide with clear sections, concrete examples, and no generic filler.
3. Add a "why this works" note for each major recommendation.
4. Include a small decision table: option, tradeoff, risk, best next action.
5. Finish with a 7-point QA checklist the team can use before shipping.

Quality bar:
- Make it usable by a small team shipping this week.
- Prefer specific wording, states, edge cases, and acceptance criteria.
- If key context is missing, ask up to three clarifying questions before the full answer.
- If you make assumptions, mark them as assumptions and keep moving.

Start by asking for the pasted context, then create "Conversion-Smart Release Bug Migration Guide".