Find the signal in a noisy log

Something went wrong: {{what_went_wrong}}. Approximate time: {{time_window}}. Here's the log: ``` {{log}} ``` 1. Ignore routine noise. List the lines that look abnormal, with timestamps: errors, warnings, retries, unusual gaps in time, and messages that only appear around the incident. 2. Put them in order and tell the story of what probably happened, step by step. 3. Mark the earliest line that looks like the start of the problem rather than a side-effect. 4. Say what's missing from the log that would confirm your theory, and what to log next time. Quote log lines exactly; don't paraphrase them.

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.