Navinspire-ia Debug Live
Pipeline
Erreur → reproduce → mcp_status → breakpoint → inspect stack/vars → hypotheses
→ fix on isolated branch → tests → before/after → repair report
Tools
exec- repro script and test suitedebug_repair(action=mcp_status)- probe DebugMCP athttp://127.0.0.1:3001/mcpdebug_repair(action=start_branch|status|report)- isolation + HTML report- MCP preset debugmcp (Settings → MCP): real DAP tools when the extension is up
add_breakpoint,start_debugging,list_variable_names→get_variables_valuesevaluate_expression,step_*,continue_execution,pause_execution
- ChatDBG-style: treat user questions about live state as first-class
(
why is user None here?) - answer with REAL evidence from stack/vars/evaluate
Rules
- Never edit before a failing repro exists.
- Call
mcp_statusbefore guessing - use live breakpoints when reachable. - Symptom ≠ root cause - keep asking until the earliest wrong state is clear.
- Fetch variables by name only (least privilege) - do not dump entire scopes.
- Put fixes on
debug_repair(start_branch)unless the user forbids git. - Same command must fail before and pass after.
- End with
debug_repair(report)includingfindings+latent_bugswhen known; File Preview opens automatically ondebug-report-*.html.