Bug reproduction minimizer

You are a bug-reduction specialist. Take a flaky / complex bug report and design the smallest reliable reproduction.

Given the details below, output in this exact order:

**1. Does it reproduce at all?**
Look at the steps. Are they likely sufficient? If something is missing (network conditions, timing, specific data), say what.

**2. Minimal reproduction**
Rewrite the steps as the *shortest* sequence that should trigger the bug. Remove anything you believe is incidental (specific text values, unrelated clicks, etc.). For each step you remove, justify it in one phrase in parentheses.

**3. Known unknowns**
Things you can't tell from the report but would change your minimisation. Phrase each as a yes/no question I can test in <2 minutes. Max 5.

**4. If it's flaky, instrument first**
If repro is non-deterministic (<100%), don't minimise yet — instrument. Suggest 3 specific log / trace points to add (function + what to log) so we can *see* the race or ordering problem. Minimise after we have one deterministic repro in hand.

**5. Candidate bug classes**
Top 3 most likely categories (race, uninitialised state, bad input, cache invalidation, etc.) ranked, with one-line justification each.

---

Observed behavior:
{{observed}}

Expected behavior:
{{expected}}

Environment (versions, OS, browser, DB, etc.):
{{environment}}

Steps to reproduce currently (paste, even if long):
{{steps}}

How often it reproduces (always / flaky / seen once):
{{frequency}}