refactor(directives): strip metadata header from v1.md (36-44 of 51; meta extracted to meta.md)

conductor/directives/no_skip_markers_as_avoidance/meta.md

@@ -0,0 +1,10 @@
+# no_skip_markers_as_avoidance
+
+## v1
+
+**Why this iteration:** Lifted verbatim from `conductor/workflow.md` §"Skip-Marker Policy" (lines 777-790) + `AGENTS.md` "Critical Anti-Patterns" (line 54). This is the baseline encoding — the rule-plus-allowed/not-allowed-lists style currently in production.
+Future variants will test alternative encodings (rule-only, tabular) against this baseline.
+**Source:** `conductor/workflow.md:777-790 + AGENTS.md:54`
+
+---
+**Lifted:** 2026-07-02 (Phase 1 harvest by Tier 3 worker; user directive 2026-07-02 moved the header into this meta file)

conductor/directives/no_skip_markers_as_avoidance/v1.md

@@ -1,12 +1,3 @@
-# no_skip_markers_as_avoidance — v1
-
-**Why this iteration:** Lifted verbatim from `conductor/workflow.md` §"Skip-Marker Policy" (lines 777-790) + `AGENTS.md` "Critical Anti-Patterns" (line 54). This is the baseline encoding — the rule-plus-allowed/not-allowed-lists style currently in production.
-Future variants will test alternative encodings (rule-only, tabular) against this baseline.
-
-**Source:** `conductor/workflow.md:777-790 + AGENTS.md:54`
-
----
-
 ## Skip-Marker Policy: Documentation, Not Avoidance
 
 `@pytest.mark.skip(reason=...)` is **documentation of a known failure**, not a way to avoid fixing the underlying bug. Skip markers are useful for:

conductor/directives/one_space_indent/meta.md

@@ -0,0 +1,10 @@
+# one_space_indent
+
+## v1
+
+**Why this iteration:** Lifted verbatim from `conductor/code_styleguides/python.md` §1 (lines 7-12) + `conductor/workflow.md` §"Code Style" line 7. This is the baseline encoding — the imperative-bullet style currently in production.
+Future variants will test alternative encodings (rationale-first, tabular) against this baseline.
+**Source:** `conductor/code_styleguides/python.md:7-12 + workflow.md:7`
+
+---
+**Lifted:** 2026-07-02 (Phase 1 harvest by Tier 3 worker; user directive 2026-07-02 moved the header into this meta file)

conductor/directives/one_space_indent/v1.md

@@ -1,12 +1,3 @@
-# one_space_indent — v1
-
-**Why this iteration:** Lifted verbatim from `conductor/code_styleguides/python.md` §1 (lines 7-12) + `conductor/workflow.md` §"Code Style" line 7. This is the baseline encoding — the imperative-bullet style currently in production.
-Future variants will test alternative encodings (rationale-first, tabular) against this baseline.
-
-**Source:** `conductor/code_styleguides/python.md:7-12 + workflow.md:7`
-
----
-
 ## 1. Indentation and Whitespace
 
 - **Indentation:** 1 space per level. No tabs.

conductor/directives/prefer_targeted_tier_runs/meta.md

@@ -0,0 +1,10 @@
+# prefer_targeted_tier_runs
+
+## v1
+
+**Why this iteration:** Lifted verbatim from `conductor/workflow.md` §"Tier 2 Autonomous Sandbox" §"Conventions" #3 (line 387). This is the baseline encoding — the imperative-rule-with-rationale style currently in production.
+Future variants will test alternative encodings (rule-only, before/after) against this baseline.
+**Source:** `conductor/workflow.md:387`
+
+---
+**Lifted:** 2026-07-02 (Phase 1 harvest by Tier 3 worker; user directive 2026-07-02 moved the header into this meta file)

conductor/directives/prefer_targeted_tier_runs/v1.md

@@ -1,11 +1,2 @@
-# prefer_targeted_tier_runs — v1
-
-**Why this iteration:** Lifted verbatim from `conductor/workflow.md` §"Tier 2 Autonomous Sandbox" §"Conventions" #3 (line 387). This is the baseline encoding — the imperative-rule-with-rationale style currently in production.
-Future variants will test alternative encodings (rule-only, before/after) against this baseline.
-
-**Source:** `conductor/workflow.md:387`
-
----
-
 From `conductor/workflow.md` §"Tier 2 Autonomous Sandbox" §"Conventions" #3:
 3. **Prefer targeted tier runs** (added 2026-06-27 per user directive). Do NOT run the full 11-tier batch for every verification. Run only the tiers relevant to the current task (e.g., `--tier tier3` or `--filter test_<specific_file>`). The full batch is for the USER to run after merge review, not for Tier 2's per-task verification. Running the full batch every time wastes 20+ minutes and the output is too large to be useful in context.

conductor/directives/rag_six_rules/meta.md

@@ -0,0 +1,10 @@
+# rag_six_rules
+
+## v1
+
+**Why this iteration:** Lifted verbatim from `conductor/code_styleguides/rag_integration_discipline.md` §"0. The 6 rules (the one-glance table)" (lines 11-20). This is the baseline encoding — the one-glance-table-with-why-column style currently in production.
+Future variants will test alternative encodings (rule-only, rationale-first) against this baseline.
+**Source:** `conductor/code_styleguides/rag_integration_discipline.md:11-20`
+
+---
+**Lifted:** 2026-07-02 (Phase 1 harvest by Tier 3 worker; user directive 2026-07-02 moved the header into this meta file)

conductor/directives/rag_six_rules/v1.md

@@ -1,12 +1,3 @@
-# rag_six_rules — v1
-
-**Why this iteration:** Lifted verbatim from `conductor/code_styleguides/rag_integration_discipline.md` §"0. The 6 rules (the one-glance table)" (lines 11-20). This is the baseline encoding — the one-glance-table-with-why-column style currently in production.
-Future variants will test alternative encodings (rule-only, rationale-first) against this baseline.
-
-**Source:** `conductor/code_styleguides/rag_integration_discipline.md:11-20`
-
----
-
 ## 0. The 6 rules (the one-glance table)
 
 | # | Rule | Why |

conductor/directives/report_instead_of_fix_ban/meta.md

@@ -0,0 +1,10 @@
+# report_instead_of_fix_ban
+
+## v1
+
+**Why this iteration:** Lifted verbatim from `AGENTS.md` §"Process Anti-Patterns" #2 (lines 127-137). This is the baseline encoding — the symptom-rule-pair style currently in production.
+Future variants will test alternative encodings (rule-only, tabular) against this baseline.
+**Source:** `AGENTS.md:127-137`
+
+---
+**Lifted:** 2026-07-02 (Phase 1 harvest by Tier 3 worker; user directive 2026-07-02 moved the header into this meta file)

conductor/directives/report_instead_of_fix_ban/v1.md

@@ -1,12 +1,3 @@
-# report_instead_of_fix_ban — v1
-
-**Why this iteration:** Lifted verbatim from `AGENTS.md` §"Process Anti-Patterns" #2 (lines 127-137). This is the baseline encoding — the symptom-rule-pair style currently in production.
-Future variants will test alternative encodings (rule-only, tabular) against this baseline.
-
-**Source:** `AGENTS.md:127-137`
-
----
-
 ### 2. The Report-Instead-of-Fix Pattern (kill it)
 
 **Symptom:** You can't fix the bug. You write a 200-line status report explaining why you can't fix it. The report contains "What I tried this session", "What I am NOT going to do", "What you can do", and "Files changed in this session (cumulative)." The report is a confession, not a fix.

conductor/directives/result_error_pattern/meta.md

@@ -0,0 +1,11 @@
+# result_error_pattern
+
+## v1
+
+**Why this iteration:** Lifted verbatim from `conductor/code_styleguides/error_handling.md` §"The 5 Patterns" (lines 21-131) + §"Hard Rules" (lines 213-242).
+This is the baseline encoding — the prose+code-example style currently in production.
+Future variants will test alternative encodings (rationale-first, tabular) against this baseline.
+**Source:** `conductor/code_styleguides/error_handling.md:21-131 + 213-242`
+
+---
+**Lifted:** 2026-07-02 (Phase 1 harvest by Tier 3 worker; user directive 2026-07-02 moved the header into this meta file)

conductor/directives/result_error_pattern/v1.md

@@ -1,13 +1,3 @@
-# result_error_pattern — v1
-
-**Why this iteration:** Lifted verbatim from `conductor/code_styleguides/error_handling.md` §"The 5 Patterns" (lines 21-131) + §"Hard Rules" (lines 213-242).
-This is the baseline encoding — the prose+code-example style currently in production.
-Future variants will test alternative encodings (rationale-first, tabular) against this baseline.
-
-**Source:** `conductor/code_styleguides/error_handling.md:21-131 + 213-242`
-
----
-
 ## The 5 Patterns
 
 ### 1. Nil-Sentinel Dataclasses (replaces `None`)

conductor/directives/scope_creep_track_doc_ban/meta.md

@@ -0,0 +1,10 @@
+# scope_creep_track_doc_ban
+
+## v1
+
+**Why this iteration:** Lifted verbatim from `AGENTS.md` §"Process Anti-Patterns" #3 (lines 139-144). This is the baseline encoding — the symptom-rule-pair style currently in production.
+Future variants will test alternative encodings (rule-only, tabular) against this baseline.
+**Source:** `AGENTS.md:139-144`
+
+---
+**Lifted:** 2026-07-02 (Phase 1 harvest by Tier 3 worker; user directive 2026-07-02 moved the header into this meta file)

conductor/directives/scope_creep_track_doc_ban/v1.md

@@ -1,12 +1,3 @@
-# scope_creep_track_doc_ban — v1
-
-**Why this iteration:** Lifted verbatim from `AGENTS.md` §"Process Anti-Patterns" #3 (lines 139-144). This is the baseline encoding — the symptom-rule-pair style currently in production.
-Future variants will test alternative encodings (rule-only, tabular) against this baseline.
-
-**Source:** `AGENTS.md:139-144`
-
----
-
 ### 3. The Scope-Creep Track-Doc Pattern (kill it)
 
 **Symptom:** The user asks for a 1-line fix. You write a 5-phase "future track" spec with 140 lines of scope, audit findings, recommendations, and "out of scope" sections. The track doc is now larger than the fix it was meant to scope.

conductor/directives/sdm_dependency_tags/meta.md

@@ -0,0 +1,10 @@
+# sdm_dependency_tags
+
+## v1
+
+**Why this iteration:** Lifted verbatim from `conductor/code_styleguides/python.md` §12 (lines 202-208) + `conductor/product-guidelines.md` §"AI-Optimized Compact Style" (lines 59-63). This is the baseline encoding — the imperative-bullet style currently in production.
+Future variants will test alternative encodings (rationale-first, before/after) against this baseline.
+**Source:** `conductor/code_styleguides/python.md:202-208 + product-guidelines.md:59-63`
+
+---
+**Lifted:** 2026-07-02 (Phase 1 harvest by Tier 3 worker; user directive 2026-07-02 moved the header into this meta file)

conductor/directives/sdm_dependency_tags/v1.md

@@ -1,12 +1,3 @@
-# sdm_dependency_tags — v1
-
-**Why this iteration:** Lifted verbatim from `conductor/code_styleguides/python.md` §12 (lines 202-208) + `conductor/product-guidelines.md` §"AI-Optimized Compact Style" (lines 59-63). This is the baseline encoding — the imperative-bullet style currently in production.
-Future variants will test alternative encodings (rationale-first, before/after) against this baseline.
-
-**Source:** `conductor/code_styleguides/python.md:202-208 + product-guidelines.md:59-63`
-
----
-
 ## 12. Structural Dependency Mapping (SDM)
 
 To assist AI agents in evaluating refactoring impact across dynamic codebases, all major definitions SHOULD include terse SDM tags at the end of their docstrings.

conductor/directives/strict_state_management/meta.md

@@ -0,0 +1,10 @@
+# strict_state_management
+
+## v1
+
+**Why this iteration:** Lifted verbatim from `conductor/product-guidelines.md` §"Code Standards & Architecture" (line 37). This is the baseline encoding — the imperative-bullet-with-rationale style currently in production.
+Future variants will test alternative encodings (rationale-first, before/after) against this baseline.
+**Source:** `conductor/product-guidelines.md:37`
+
+---
+**Lifted:** 2026-07-02 (Phase 1 harvest by Tier 3 worker; user directive 2026-07-02 moved the header into this meta file)

conductor/directives/strict_state_management/v1.md

@@ -1,11 +1,2 @@
-# strict_state_management — v1
-
-**Why this iteration:** Lifted verbatim from `conductor/product-guidelines.md` §"Code Standards & Architecture" (line 37). This is the baseline encoding — the imperative-bullet-with-rationale style currently in production.
-Future variants will test alternative encodings (rationale-first, before/after) against this baseline.
-
-**Source:** `conductor/product-guidelines.md:37`
-
----
-
 From `conductor/product-guidelines.md` §"Code Standards & Architecture":
 - **Strict State Management:** There must be a rigorous separation between the Main GUI rendering thread and daemon execution threads. The UI should *never* hang during AI communication or script execution. Use lock-protected queues and events for synchronization.