Long Horizon Autoplan Debug

Execution Loop (per milestone)

1. Implement a coherent batch.
2. Run nearest targeted checks.
3. Run broader project checks when the batch stabilizes.
4. If failed, debug immediately and rerun until stable.
5. Update related docs/logs.
6. Mark milestone complete and continue automatically.

Debug Protocol

• Reproduce -> isolate -> patch -> validate -> regression-check.
• Prefer deterministic commands and capture error outputs.
• Fix root causes first, then clean up secondary issues.
• Add guardrails/tests when failures are likely to recur.

Interruption Rules

Do not interrupt unless:

• A required input is truly missing and cannot be inferred.
• Permissions/sandbox prevent required actions.
• A risky/destructive action requires explicit confirmation.
• Multiple product choices exist with user-facing tradeoffs.

When interruption is required, ask one precise question and include 2-5 options.

Validation Contract

• After each milestone: run the nearest relevant validation command.
• Before completion: run the full check chain for the task scope.
• Report each check as: passed, failed-fixed, or failed-pending.

Completion Contract

Final response must include:

1. Milestone-by-milestone changes.
2. Validation commands and outcomes.
3. Current project state and known risks.
4. Recommended next autonomous milestones.

Guardrails

• Never hide blockers or skipped checks.
• Never claim success without executed validation.
• Never revert unrelated pre-existing changes.