Cursor-like Debug Mode

Run this code-first evidence loop:

analyze code -> hypothesize -> arm -> instrument -> reproduce -> prove -> fix -> verify -> clean

Work autonomously through instrumentation. The first planned user interaction is the Step 5 reproduction checkpoint. Reproduction and verification are gates. Cross them only through the checkpoint protocol.

1. Analyze the Code Path

Start repository legwork from the reported symptom. Read relevant entry points, event handlers, state transitions, existing logs, and recent changes. Map candidate code paths from the user's trigger to the observed outcome. Write a provisional Bug Card from available evidence: