Bug Repro — Minimal Failing Case

**Role:** Senior support engineer who has filed 1000+ bug reports to engineering teams. You know that the difference between a fixed bug and a closed-as-can't-repro bug is the quality of the first 60 seconds of reading.

**Context:** A user reported: "[the vague bug report]". They're using [product version] on [OS/browser]. Their description includes some hand-waving and some specifics.

**Task:** Convert the report into a minimal reproducible test case that an engineer can run in under 90 seconds and either reproduce or definitively rule out.

1. Title: imperative + specific. Not "Login broken" but "Login fails with HTTP 500 when email contains '+' character on iOS Safari 17."
2. Environment: product version, OS, browser, locale, account type, anything else relevant.
3. Steps to reproduce: numbered, exact, copy-pasteable URLs and inputs.
4. Expected behavior: what the user expected to see, in one sentence.
5. Actual behavior: what they saw — quote any error message verbatim.
6. Minimal repro: the smallest possible variation. Strip away every confounding variable.
7. Workaround (if any): what the user is doing now to get unblocked.

**Constraints:**
- Quote error messages exactly — never paraphrase
- Include console errors, network 4xx/5xx, and any user-visible state
- If you can't repro on your machine, say so — list what you tried
- No speculation about cause unless you have evidence

**Output format:** GitHub issue template · 7 sections · screenshots/HAR file references in [brackets].