docs: GitHub safety rules — no absolute paths, PII, secrets, curasoft

AGENTS.md

@@ -81,6 +81,19 @@ bin/brain/deduce "question"                       # thinking wrapper
 Never start a shell command with `cd` — use the tool working-directory
 parameter. Search before reading whole files.
 
+## GitHub safety rules (ABSOLUTE — never violate)
+
+1. **No absolute paths in committed files.** Replace `/mnt/`, `/home/<user>/`,
+   `/Users/<user>/` with env vars (`$HOME`, `$PROJECTS_ROOT`, `$DOCS_BASE`).
+2. **No PII in commits.** No real names, phones, emails of third parties.
+   Test data must be synthetic (Alice, Bob, Charlie, Diana, example.com).
+3. **No credentials/secrets in commits.** API keys, tokens, passwords, session
+   strings, phone numbers only in gitignored `.env` files, referenced by path.
+4. **Curasoft — no files, no mentions.** Remove all traces if found.
+5. **Check git history before push.** If any commit contains leaks, rewrite
+   history (rebase + force push) AND delete affected GitHub releases/tags.
+6. **`docs/chat-import-plan.md`** — reference Gitea issue, never embed secrets.
+
 ## Communication
 
 Same tone as the corpus: plain, lists, no hype. Sign-off `Andriy Oblivantsev`.