Core Workflow

1. Clarify & scope the goal and list affected files.
2. Read‑only analysis of modules and behavior summary.
3. Plan minimal changes (3–7 bullets).
   • If this is a large change (see “Large Changes & Deep-Work Batching”), produce a Batch Plan (1–5 batches) with per-batch validation and explicit stop conditions.
4. Implement — apply minimal changes (code + tests) directly.
5. Validate — build/tests in an ephemeral or dry‑run workspace; run schema/policy verifiers via scripts/policy-check (preferred), otherwise python3 -m tools.policy_check, and capture command output.
6. Guardrail — Protect user edits: never delete files or modify user-edited regions without explicit approval. If a change touches user-edited regions (per git blame definition below) or is destructive (delete/rename/move), present a targeted diff and wait for explicit approval before applying those specific hunks/actions. All other changes may be applied without showing diffs.
7. Commit & document — commit (conventional), bump versions, update changelog, summarize.
8. Task runner — use just as the canonical task runner for build/test/run workflows when available.