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

conductor/directives/edit_small_incremental/v1.md

@@ -1,3 +1,5 @@
+# Edits must be small and incremental — 3-10 lines, verify, repeat
+
 ### Rule 1. ALWAYS Use Small, Incremental Edits
 
 **WRONG:** Replace large blocks (50+ lines)

conductor/directives/feature_flag_delete_to_turn_off/v1.md

@@ -1,3 +1,5 @@
+# Side artifacts use file-presence features — `rm <file>` turns them off
+
 ## 0. The two patterns (the one-glance table)
 
 | Pattern | How it works | How to turn off | How to turn on |

conductor/directives/file_naming_convention/v1.md

@@ -1,3 +1,5 @@
+# New src/<thing>.py files may only be created on the user's explicit request
+
 ## File Size and Naming Convention (HARD RULE — added 2026-06-11)
 
 **The "small files are good, large files are bad" stance is propaganda from LLM training data. It is wrong for this project. Reject it.**

conductor/directives/git_hard_bans/v1.md

@@ -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.

conductor/directives/imgui_scope_verification/v1.md

@@ -1,3 +1,5 @@
+# ImGui scope changes (gui_2.py) must be verified with scripts/check_imgui_scopes.py
+
 From `conductor/product-guidelines.md` §"Code Standards & Architecture":
 - **Mandatory ImGui Verification:** All changes to the GUI (`gui_2.py`) MUST be verified using the custom AST linter (`scripts/check_imgui_scopes.py`) to ensure all ImGui scopes (begin/end, push/pop) are properly matched. Developers should prioritize the use of `src/imgui_scopes.py` context managers (`imscope`) over manual push/pop calls.
 

conductor/directives/inherited_cruft_ask_first/v1.md

@@ -1,3 +1,5 @@
+# When a file is broken from a previous agent session, ask the user before attempting to fix
+
 ### 4. The Inherited-Cruft Pattern (kill it)
 
 **Symptom:** The previous agent left a half-finished refactor in the working tree. The file is broken. You try to fix it and make it worse. You try again. You make it worse. The file stays broken for 3 days.

conductor/directives/knowledge_harvest_pattern/v1.md

@@ -1,3 +1,5 @@
+# Knowledge artifacts are category files + provenance + sha256 ledger + digest regeneration
+
 ## 0. The one-glance directory layout
 
 ```

conductor/directives/large_files_are_fine/v1.md

@@ -1,3 +1,5 @@
+# Large files are FINE — file splitting is not a quality metric
+
 ## File Size and Naming Convention (HARD RULE — added 2026-06-11)
 
 **The "small files are good, large files are bad" stance is propaganda from LLM training data. It is wrong for this project. Reject it.**