feat(directives): add 15 engagement-specific directives + tags.toml entries

conductor/directives/doc_update_after_track_ships/meta.md

@@ -0,0 +1,9 @@
+# doc_update_after_track_ships
+
+## v1
+
+**Why this iteration:** New rule, no prior source. Encodes the existing "Documentation Refresh Protocol" from `conductor/workflow.md` as a directive.
+**Source:** new rule (pattern from `conductor/workflow.md` "Documentation Refresh Protocol")
+
+---
+**Lifted:** 2026-07-05

conductor/directives/doc_update_after_track_ships/v1.md

@@ -0,0 +1,14 @@
+# After a track ships, update the affected `docs/guide_*.md` to reflect the new module structure
+
+## What it says
+
+When a track changes the shape of a module (renames a file, moves a system, adds a new system file), the implementing agent MUST update the corresponding `docs/guide_*.md` to reflect the new structure. This is part of the track's final phase — not a follow-up track.
+
+## Why
+
+A track that only changes code (not docs) is incomplete. The next agent reads `docs/guide_*.md` to understand the module; if the guide is stale, the agent's mental model is wrong from the start. The documentation refresh is the track's handoff to the next agent.
+
+## See also
+
+- `conductor/directives/end_of_track_report_required` — the TRACK_COMPLETION report
+- `conductor/directives/chronology_must_regenerate_after_every_track_ship` — the chronology regeneration