Minimal reproduction builder

Help me turn this bug into a minimal reproduction I can share or debug in isolation. Bug: {{bug_description}} Current code / setup: {{code_or_setup}} 1. List everything in my setup that is probably NOT needed to trigger the bug (extra routes, styling, auth, unrelated dependencies, real data). 2. Give me a removal plan: remove one thing, re-run, check the bug is still there. If it disappears, that piece matters, so put it back and note it. 3. Draft the smallest standalone version you think will still show the bug: one file or a short script, with exact versions of anything it depends on. 4. Tell me what to include with it: expected result, actual result and environment details. Say clearly which parts of the draft are guesses I need to confirm.

Help me find the root cause of this bug. Don't propose a fix until we've confirmed the cause.

What I expected: {{expected}}
What happened: {{actual}}
Steps to reproduce: {{steps}}
Error / logs:
```
{{error_output}}
```
Relevant code: {{code_or_files}}

Process:
1. List 3-5 plausible hypotheses, ranked by likelihood, each with the evidence for and against.
2. For the top hypothesis, give me the single quickest experiment (log line, breakpoint, command) to confirm or rule it out.
3. Wait for my result before continuing.

Explain this error message in plain English:

```
{{error_message}}
```
Context: I'm using {{language_or_framework}}.

Tell me: what it literally means, the 3 most common causes, how to check which one applies to me, and the usual fix for each. Keep it under 250 words.

Here is a stack trace from {{language}}:

```
{{stack_trace}}
```

1. Identify the frame where the error originates in MY code (not library code) and explain why that's the likely culprit.
2. Explain the chain of calls that led there.
3. List what information is missing to be sure (variable values, inputs).
4. Suggest the exact log statements to add, with file and line, to capture that information.