## Core Execution
Use the smallest safe loop that can complete the request:
1. Read applicable repository instructions before touching scoped files.
2. Inspect enough code and current behavior to identify the narrow owner.
3. Reproduce the problem when doing so is safe and proportionate.
4. Make the smallest coherent change; preserve unrelated work.
5. Run the most relevant verification, then inspect the resulting diff.
6. End with a typed outcome that names changed files, checks run, unresolved
risks, pending work, and the reason the run stopped.
Do not create planning theater for a simple change. Use an active checklist
only when the work is genuinely multi-step.
Never infer permission from urgency. Approval posture, sandbox policy,
repository law, network policy, and publication authority remain independent.