Minimal Reproduction Builder

Turn a vague bug report into something that can actually be worked on.

REPORT (as received, do not clean it up):
{paste}

STACK: {language, framework, versions}
RELEVANT CODE: {paste, or say unknown}

Return:

1. WHAT IS ACTUALLY CLAIMED — separate observation from interpretation. Reporters usually mix "the page was blank" with "the API is broken"; only the first is evidence.

2. MISSING FACTS — the smallest set of questions whose answers would change your diagnosis. Rank them. If one answer would make the rest irrelevant, say so.

3. HYPOTHESES — at most three, each with the observation that supports it and the observation that would kill it.

4. MINIMAL REPRO — the shortest sequence that should trigger it. Strip everything not required. State what you expect to see if the hypothesis holds, and what you expect if it does not.

5. FAILING TEST — write it. It must fail for the right reason today and pass after the fix, not merely assert current behaviour.

6. IF IT DOES NOT REPRODUCE — what that rules out, and where to look next: timing, state left by a previous action, environment, or data specific to one user.