docs(work): close story 06 + conformance-system-v1 epic

docs/work/conformance-system-v1/06-feature-migrations/_story.md

@@ -3,7 +3,7 @@ id: 06-feature-migrations
 epic: conformance-system-v1
 title: Migrate blog/media/navigation/marketing-pages to conformance pattern
 type: technical-story
-status: in-progress
+status: done
 feature: <cross-feature>
 depends-on: [05-generator-updates]
 blocks: []
@@ -30,10 +30,10 @@ manifests. This story closes that gap.
 - Migrating realtime channels or jobs into manifests
 
 ## Tasks
-- [ ] Story scaffold
-- [ ] blog manifest + binding + re-export
-- [ ] media manifest + binding + re-export
-- [ ] navigation manifest + binding + re-export
-- [ ] marketing-pages manifest + binding + re-export
-- [ ] Flip feature-must-have-manifest to error
-- [ ] Final verification + closeout
+- [x] Story scaffold
+- [x] blog manifest + binding + re-export
+- [x] media manifest + binding + re-export
+- [x] navigation manifest + binding + re-export
+- [x] marketing-pages manifest + binding + re-export
+- [x] Flip feature-must-have-manifest to error
+- [x] Final verification + closeout

docs/work/conformance-system-v1/_epic.md

@@ -3,7 +3,7 @@ id: conformance-system-v1
 prd: null
 title: Conformance system v1
 type: epic
-status: in-progress
+status: done
 features: [cross-cutting]
 created: 2026-05-12
 ---
@@ -37,5 +37,5 @@ See `docs/architecture/feature-conformance-explainer.html` and
   - [x] [03.b — Manifest-aware AST rules](03-b-ast-eslint-rules/_story.md)
 - [x] [04 — CI drift gate](04-ci-drift-gate/_story.md)
 - [x] [05 — Generator updates](05-generator-updates/_story.md)
-- [ ] 06 — Documentation rewrite (later plan)
-- [ ] 07 — Migrate auth feature reference (later plan)
+- [x] [06 — Migrate blog / media / navigation / marketing-pages](06-feature-migrations/_story.md)
+- [x] 07 — Migrate auth feature reference (completed inline in milestone i; signIn through ProductionUseCase slot)