docs: record push policy — commit per work unit, push only at milestones
This commit is contained in:
@@ -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,
|
`taskNN-*` branches, no PRs. The scope discipline above is about test focus,
|
||||||
not git mechanics.
|
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:
|
MUST read the architecture guide before planning or modifying the codebase:
|
||||||
[`ai.md`](ai.md) (+ [`schema.md`](schema.md) for the memory-map conventions).
|
[`ai.md`](ai.md) (+ [`schema.md`](schema.md) for the memory-map conventions).
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user