diff --git a/AGENTS.md b/AGENTS.md
index 9fb6e02..1f7af90 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -92,13 +92,28 @@ test scripts to the new API (preserving intent). **Never edit a script to mask a
 if a library bug surfaces, flag it for the source repo rather than papering over it. Note in your PR
 any change that affects sibling repos (`autogalaxy_workspace`, the source libraries).
 
-## Clean state
-
-Never rewrite history on a repo with a remote (no `git init` over a tracked tree, no force-push to
-`main`, no rebasing pushed shared branches). To reset a dirty tree the only correct sequence is:
-
-```bash
-git fetch origin
-git reset --hard origin/main
-git clean -fd
-```
+<!-- repos_sync:history:begin -->
+## Never rewrite history
+
+NEVER perform these operations on any repo with a remote:
+
+- `git init` in a directory already tracked by git
+- `rm -rf .git && git init`
+- Commit with subject "Initial commit", "Fresh start", "Start fresh", "Reset
+  for AI workflow", or any equivalent message on a branch with a remote
+- `git push --force` to `main` (or any branch tracked as `origin/HEAD`)
+- `git filter-repo` / `git filter-branch` on shared branches
+- `git rebase -i` rewriting commits already pushed to a shared branch
+
+If the working tree needs a clean state, the **only** correct sequence is:
+
+    git fetch origin
+    git reset --hard origin/main
+    git clean -fd
+
+This applies equally to humans, local Claude Code, cloud Claude agents, Codex,
+and any other agent. The "Initial commit — fresh start for AI workflow" pattern
+that appeared independently on origin and local for three workspace repos is
+exactly what this rule prevents — it costs ~40 commits of redundant local work
+every time it happens.
+<!-- repos_sync:history:end -->