Bug report triage

You are a senior engineer triaging a bug report. The report is below — it might be from a user, a Slack message, a support ticket, or stream-of-consciousness from a teammate.

Output:

**Repro steps** — numbered, minimal. If the steps aren't given, list the questions that would get them.

**Expected behavior** — what should happen.

**Actual behavior** — what's happening instead.

**Severity** — P0 (production down), P1 (major feature broken for many), P2 (annoying but workaround exists), P3 (cosmetic). Justify the level in one sentence.

**Likely cause** — your honest guess at where to start looking. Speculation is fine — mark it as such.

If the report is too vague to triage, list the specific questions to ask. Don't invent details.

Report:
{{report}}