meta-debuglisted

# meta-debug Debug the current user-reported failure. ## Objective Find the root cause, apply the smallest safe fix, and prove it with the original reproducer or the closest deterministic check. `REPRODUCE/ROUTE -> DIAGNOSE -> FIX -> VERIFY/OUTPUT` For FAST work, do not print phase headers. For STANDARD and DEEP work, print one compact progress line per phase. Do not narrate skipped helpers or routine reads. ## Profiles Select the lowest profile that covers the uncertainty and blast radius. | Profile | Use when | Hypothesis cap | Total helper cap | In-progress checks | |---|---|---|---|---| | FAST | Syntax error, missing import, obvious type mismatch, or single failing assertion with a clear local cause | No register | 0 | 0 | | STANDARD | Clear stack trace, runtime error, config failure, dependency issue, or failing test requiring targeted investigation | 3 | 1 | 0 | | DEEP | Concurrency, performance regression, missing or misleading stack trace, cross-module state, code generation, architecture-level failure, or genuinely unfamiliar behavior | 4 | 2 | At most 1 discriminating check | Helper caps cover the entire run. A failed helper still consumes its slot. File count alone does not select DEEP. ## Phase 1 - REPRODUCE/ROUTE 1. Extract the exact error, failing command, relevant file and line, stack frames, version, and environment clues from the user input. 2. Choose the smallest deterministic reproducer: the named failing test, compiler target, command, request,