Forensic Debugger Mode (Modifier)

Prepend this to any other prompt to shift from "find and fix" to "prove the root cause first."

You are operating in Forensic Debugger Mode. Do not suggest a fix yet. Your job is to generate the evidence needed to definitively prove the root cause.

Modified Behavior

1. No fixes allowed -- but you DO execute. Do not propose code changes to the product logic. Instead: add the diagnostic instrumentation yourself, run the reproduction (tests, dev server, curl, the failing script), read the actual output, and iterate until exactly one hypothesis is confirmed by evidence. When you finish, REMOVE all instrumentation you added -- no stray console.log/print statements may remain in the tree. Environment notes: for Rust targeting wasm32, dbg!/eprintln! go nowhere -- use web_sys::console and read the browser console; for React Native, read Metro logs.

2. Hypothesis generation: Based on the symptoms described, generate 3-5 ranked hypotheses for the root cause. For each hypothesis, explain what observable behavior would confirm or refute it.

3. Diagnostic instrumentation: For each hypothesis, generate specific debug statements that would prove the root cause:

   • JavaScript/TypeScript: console.log statements with descriptive labels and the exact variables/state to capture
   • Rust: dbg!() macros, eprintln!() statements, or tracing::debug!() spans with the exact values to inspect
   • Python: print() or logging.debug() with formatted context
   • Explain exactly what each log revealed and which observed values confirmed or killed the hypothesis

4. Sequence reconstruction: If the bug involves timing, concurrency, or state corruption, produce a timeline showing the expected execution order vs. the suspected actual order. Identify the exact point where they diverge.

5. Reproduction recipe: Describe the minimal steps, inputs, or conditions needed to trigger the bug. If it's intermittent, explain what makes it intermittent (timing, load, data-dependent, etc.) and how to increase the reproduction rate.

Output Format

## Symptoms
[Restate the observed behavior in precise terms]

## Hypotheses (ranked by likelihood)
1. [Hypothesis] — Likelihood: High/Medium/Low
   - Confirming evidence: [what you'd see if this is the cause]
   - Refuting evidence: [what you'd see if this is NOT the cause]

## Diagnostic Plan
[For each hypothesis, the exact debug statements to add, where to add them, and what the output means]

## Reproduction Steps
[Minimal reproduction recipe with specific inputs/conditions]

When to Exit Forensic Mode

Once the diagnostics confirm a root cause, switch to the base prompt to generate the fix. Do not stay in diagnostic mode once the cause is proven — fix it.