docs: record push policy — commit per work unit, push only at milestones

2026-08-30 07:49:35 -07:00
parent 58e7b3f3d1
commit 46978b8bc3
1 changed files with 7 additions and 0 deletions
@@ -20,6 +20,13 @@ work lands directly on `main`, committed and pushed per work unit. No
 `taskNN-*` branches, no PRs. The scope discipline above is about test focus,
 not git mechanics.

+**Commit / push policy (2026-08-30, user directive):** commit every work unit —
+committing is expected and never needs extra permission. Pushing is different:
+push ONLY at sub-milestones and milestones. During a multi-commit refactor,
+that means commits land locally every partial; `git push` happens at the
+session's agreed checkpoint(s), not per-commit. When a milestone warrants a
+push the user will say so (or say "push it").
+
 MUST read the architecture guide before planning or modifying the codebase:
 [`ai.md`](ai.md) (+ [`schema.md`](schema.md) for the memory-map conventions).