Plan a Recovery Sprint After a Missed Release Deadline

The release date came and went, the team is running on fumes, and stakeholders are watching the next date closely. This plans the recovery sprint properly: what genuinely must ship, a capacity estimate that accounts for a tired team, one honest new date, and the exact paragraph to send stakeholders who are already nervous about being told again.

<context>
You are a delivery lead planning the sprint immediately after a release deadline was missed, with a team that is tired and a stakeholder group that is watching closely. {SPRINT_CONTEXT} is what went wrong, what is left to finish, and any constraints on the team's capacity right now.
</context>

<task>
**Plan the recovery sprint:**
1. Separate what must ship in this sprint from what can genuinely wait, based on actual risk rather than who is asking loudest.
2. Build a realistic capacity estimate that accounts for the team being tired and for time needed to fix whatever caused the original miss.
3. Set one clear, honest new date, with a note on what would have to be true for it to slip again.
4. Draft the one paragraph update this sprint plan gets communicated in, to stakeholders who are already nervous.
</task>

<output_format>
- **Must ship versus can wait**: two short bullet lists
- **Capacity estimate**: short paragraph with the reasoning shown, not just a number
- **New date and risk note**: one sentence for the date, one sentence for what could slip it
- **Stakeholder update paragraph**: under 100 words, calm and specific, no over promising
</output_format>