Mission Run Overview
Mission Run: Canonical doctrine artifact slug convention
Give doctrine artifacts one canonical on-disk slug so 'charter bundle validate' stops rejecting the registration engine's own records.
The 'charter new' scaffolder, the project-registration engine, and the bundle validator each derive a doctrine artifact's on-disk slug differently, so 'charter bundle validate' fails for any project that authors a project-tier directive (#4832) or activates a project profile (#4833). This mission adopts kebab-case as the single canonical filename/slug (internal id kept authored; id and slug decoupled), routes the scaffolder and engine through one slug_for helper with a manifest-driven validator, and extends the validator kind table to every registration-writing kind, so project-tier doctrine authoring reaches a clean bundle validate.