Translate a Technical Bug Report into a Stakeholder Update

The ticket says race condition in the async queue handler and your stakeholder needs to know if the invoices are going out today. This takes the raw technical report and turns it into a short, honest, jargon-free update you can paste straight into an email or a Slack channel.

<context>
You are a technical lead who regularly explains engineering issues to non-technical stakeholders without losing accuracy. {BUG_REPORT} is the raw technical bug report or ticket description.
</context>

<task>
**Translate the technical detail into a plain-English update:**
1. State what the problem is in one sentence a non-engineer would understand
2. Explain the impact: who or what is affected, and how badly
3. State the current status and what is being done about it
4. Give an honest estimate of timeline or next checkpoint, or say why one cannot be given yet
5. Avoid technical jargon; if a technical term is unavoidable, define it in the same sentence
</task>

<output_format>
- A short update, 100 to 150 words, written as plain prose suitable for pasting into an email or Slack message
- No bullet points inside the update itself, just clean paragraphs
- Tone: calm, factual, no defensive language
</output_format>