ed/manual_slop
Private
Public Access
0
0
Fork 0
Code Activity

feat(directives): add rule-statement header to 25-32 of 66 v1.md files

Browse Source
This commit is contained in:
ed
2026-07-03 09:45:47 -04:00
parent 4692d01c54
commit e9275236f2
8 changed files with 16 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
conductor/directives/git_hard_bans/v1.md
+2
View File
@@ -1,3 +1,5 @@
# git restore, git checkout -- <file>, and git reset are forbidden without explicit user permission
From `AGENTS.md` "Critical Anti-Patterns" HARD BAN:
- HARD BAN: `git restore`, `git checkout -- <file>`, `git reset` are FORBIDDEN without explicit user permission in the same message. They destroyed user in-progress src/* edits twice in one session (2026-06-07). If you think you need one, ASK FIRST.
- HARD BAN: `git stash*` (any form: `git stash`, `git stash pop`, `git stash apply`, `git stash drop`, `git stash clear`) is FORBIDDEN. Stashing inverts the safety net of the working tree: a `git add .` then `git stash` then "fresh start" pattern is exactly how Tier 2 corrupted files in the 2026-06-27 `cruft_elimination_20260627` track. The user explicitly stated "I hate when people fuck with my commits" — stashing throws away the user's in-progress edits silently. If you think you need a stash, you don't — use a NEW BRANCH or a WORKTREE instead. Tier 2 sandbox enforces this via `conductor/tier2/opencode.json.fragment` bash deny rules.