Rule: memory update ships in the SAME commit as the feature — follow-up docs backfill commits are a broken rule

AGENTS.md

@@ -41,8 +41,10 @@ at a problem.
 
 - **Never work without the map.** If the map contradicts the code, the code wins
   and the map gets fixed in the same change (stale facts are corrected, not appended).
-- **Every feature change ships with its memory update:** `ai.md` for
-  architecture/patterns, `TASKS.md` for status, index files when layout changes.
+- **Every feature change ships with its memory update in the SAME commit:**
+  `ai.md` for architecture/patterns, `TASKS.md` for status, index files when
+  layout changes. No code commit without its docs — a follow-up "docs backfill"
+  commit is a broken rule, not a style.
 - **Rewrite `HANDOFF.md` at session end, compaction, or any interruption.**
   Never end a session with uncommitted work unrecorded — the handoff names the
   branch, the dirty files, and why it stopped.

schema.md

@@ -52,6 +52,8 @@ that every other memory file follows. Read `ai.md` first; this file explains
 
 ## Integration rule
 
-Every feature change ships with its memory update: `ai.md` for architecture /
-patterns, `TASKS.md` for status, index files when the layout changes. That is
-what keeps the map accurate enough to trust next session.
+Every feature change ships with its memory update **in the same commit**:
+`ai.md` for architecture / patterns, `TASKS.md` for status, index files when
+the layout changes. No code commit without its docs — a follow-up "docs
+backfill" commit is a broken rule, not a style. That is what keeps the map
+accurate enough to trust next session.