From 46978b8bc32e4e2575233379df20dc30011a4692 Mon Sep 17 00:00:00 2001 From: gramps Date: Sun, 30 Aug 2026 07:49:35 -0700 Subject: [PATCH] =?UTF-8?q?docs:=20record=20push=20policy=20=E2=80=94=20co?= =?UTF-8?q?mmit=20per=20work=20unit,=20push=20only=20at=20milestones?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- AGENTS.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index b13a37a..5f0bc29 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -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).