autoresearch:fix

EXECUTE IMMEDIATELY.

Parse Arguments

Extract from $ARGUMENTS:

• Target: or --target — command that shows errors (e.g., npm test, tsc --noEmit)
• Scope: or --scope — file globs to modify
• Guard: or --guard — safety command (must always pass)
• Iterations: or --iterations — default 20. "unlimited" for unbounded.
• --from-debug — read handoff.json from previous debug run
• --category — filter: test, type, lint, build
• --evals, --evals-interval N, --chain

Setup (if required context missing)

If Target and Scope both missing:

1. Auto-detect failures: run test suite, type checker, linter, build
2. Present results via AskUserQuestion (single batched call): Q1 (Fix What): "Found [N] test failures, [M] type errors, [K] lint errors. Fix what?" — everything, only tests, only types, only lint Q2 (Guard): "Safety command that must always pass?" — npm test, tsc, npm run build, skip Q3 (Scope): "Which files can I modify?" — suggested globs from error locations + all Q4 (Launch): "Ready?" — fix until zero, fix with limit, cancel If all provided → skip setup. If --from-debug → read handoff.json for scope and findings.

Precondition Checks

Verify: git repo exists, clean working tree, no lock files, no detached HEAD. Fail fast on critical issues.

Establish Baseline (Iteration 0)

1. Run Target command → count errors (metric = error count, direction = lower_is_better)
2. Record baseline in TSV
3. Create output directory: autoresearch/fix-{YYMMDD}-{HHMM}/
4. TSV header: # metric_direction: lower_is_better\niteration\ttimestamp\terror_type\terror_fixed\tcommit\tmetric\tdelta\tguard\tstatus\tdescription

Iteration Loop (until zero errors or max_iterations)

Phase 1: Review

• Read results TSV + git log
• Run Target to get current error list
• If error count == 0 → exit loop (SUCCESS)

Phase 2: Prioritize

Order: crash/fatal → test failures → type errors → lint → warnings. Within category: easiest first (single-file fixes before cross-file).