From cf69bf0b1b106df4c8fed3499d4f2d1ca6eb14eb Mon Sep 17 00:00:00 2001
From: 2RE <torrey@nommesen.com>
Date: Thu, 10 Sep 2026 20:06:41 +0800
Subject: [PATCH] told it not to commit and push unless I tell it to

---
 memory-bank/activeContext.md | 10 ++++++++++
 memory-bank/progress.md      |  3 +++
 memory-bank/techContext.md   |  3 +++
 3 files changed, 16 insertions(+)

diff --git a/memory-bank/activeContext.md b/memory-bank/activeContext.md
index b0ed9b8..f71e3e8 100644
--- a/memory-bank/activeContext.md
+++ b/memory-bank/activeContext.md
@@ -3,6 +3,13 @@
 > Current focus, recent changes, next steps, and active decisions.
 > Last updated: 2026-09-10.
 
+## Working Agreements (read first)
+- **Never `git commit` or `git push` without explicit approval.** Do the work,
+  verify it, then STOP and ask. Approval covers that one action only; every future
+  commit and push needs its own yes.
+- Until approval, leave finished work in the working tree as uncommitted changes,
+  and say plainly what is sitting there waiting.
+
 ## Current Work Focus
 **Build phase.** A working static site on a locally vendored Bootstrap 5.3.3,
 with custom CSS/JS and a live Web3Forms contact page. It now includes a
@@ -140,6 +147,7 @@ Next is user review of copy/design and the deployment decision.
 | 18 | Site is published | ✅ Done |
 | 19 | Keep `memory-bank/` and `.clinerules/` tracked in the repo | ✅ Done |
 | 20 | `TODO.md` at the repo root is the backlog; the memory bank points at it | ✅ Done |
+| 21 | **No `git commit` or `git push` without explicit user approval** | ✅ Active rule |
 
 ### Open Questions (remaining)
 1. **Real assets:** any real favicon, Open Graph/social image, or logo to add?
@@ -148,6 +156,8 @@ Next is user review of copy/design and the deployment decision.
 4. **Live URL:** where is the published site? Nothing in the repo states it.
 
 ## Important Patterns & Preferences
+- **Git is user-gated:** never `git commit` or `git push` without explicit approval
+  (see Working Agreements at the top of this file).
 - **Backlog convention:** `TODO.md` at the repo root is the human-facing list of
   open work. The memory bank keeps only the current priorities and points there,
   so the two never drift. Issues (Forgejo) are for items that need discussion.
diff --git a/memory-bank/progress.md b/memory-bank/progress.md
index 85ed52a..22fb84c 100644
--- a/memory-bank/progress.md
+++ b/memory-bank/progress.md
@@ -191,3 +191,6 @@ copy/design review and the optional polish tracked in `TODO.md`.
   one exception is `printtiresad.png`, kept as PNG because WebP made it bigger.
   Verified: 0 missing references, 0 unreferenced files, all 45 WebP files decode,
   all pages 200, and the before/after ratio-hint sets are byte-identical.
+- **2026-09-10** - User set a **working agreement**: no `git commit` or `git push`
+  without explicit approval. Recorded in `activeContext.md` (Working Agreements at
+  the top, plus the decisions log) and `techContext.md` (Tool Usage Patterns).
diff --git a/memory-bank/techContext.md b/memory-bank/techContext.md
index c860a6e..8321d35 100644
--- a/memory-bank/techContext.md
+++ b/memory-bank/techContext.md
@@ -87,5 +87,8 @@ No build step and no package manager - it is plain static HTML/CSS/JS.
 - Work data should have a single source of truth.
 
 ## Tool Usage Patterns
+- **Never `git commit` or `git push` without explicit approval from the user.** Make
+  the edits, verify them, then stop and report; leave the work uncommitted until
+  told otherwise. Approval is per action, not standing.
 - Follow project conventions once established; verify each change (validate HTML,
   check asset paths, check responsive behavior) before reporting done.