execution-looplisted

# Execution Loop ## Intent Use a consistent execution loop that balances speed with correctness: - plan first for non-trivial work - review your own plan before implementing - ensure regression test coverage exists before changing code - re-plan when assumptions break - review your own implementation before marking done - prove behavior before marking done - keep scope minimal and deterministic ## Workflow 1. **Load minimal context**: read only the task-relevant code, docs, and configuration. Avoid broad context loading unless the task proves it necessary. 2. **Plan**: write a short, checkable execution plan. Include verification steps, not only implementation steps. 3. **Review your plan**: before implementing, review the plan as if you are the architect. Check: does it fit the architecture boundaries? Is it the smallest valuable change? Does it preserve existing contracts? Are there simpler alternatives? Iterate until there are no material issues. 4. **Ensure regression coverage**: before changing code, check that the behavior you are about to modify has existing test coverage. If it does not, add tests for the current behavior first and commit them separately. This establishes a regression baseline — if your change breaks something, the test suite catches it. 5. **Execute**: implement the minimal-impact change. Preserve existing contracts unless the task explicitly calls for changing them. 6. **Re-plan on breakage**: if an assumption fails, stop and re-plan before con