Develop locally
Make one bounded change against the pinned toolchain and current vertical slice.
Outcome
A local change preserves the working research story, generated contracts, public-tree policy, and its own normal and failure proof.
Prerequisites
Complete local setup, read the nearest AGENTS.md, and inspect git status.
Existing changes may belong to another task; do not revert or stage them broadly.
Steps
- Locate the owning module and current contract before designing.
- Implement the smallest complete vertical behavior and its tests.
- Regenerate OpenAPI/client only when the canonical API changed.
- Regenerate docs reference only when its owning Python/OpenAPI truth changed.
- Update the user/operator page and execution ledger with the slice.
- Run the narrow test, then the repository check.
pnpm checkDo not add a package, interface, service, table, compatibility branch, or fallback without a present consumer or security seam.
Verify
Prove one normal path, one failure path, and the integration edge that crosses the changed boundary. For user-facing work, run the complete reachable browser and accessibility matrix.
Recover
If another lane changed an overlapping contract, stop editing that path and coordinate the smallest shared correction. Preserve unrelated work and repair from current state rather than resetting it.