epic: content-model - Deliver structured Markdown content foundations #349

Coordinate the content-model plan and structured Markdown foundations for all eight website content types. Cover shared and type-specific fields, frontmatter schemas, operational Markdown profiles, validation, migration and content-loading contracts. Keep module functionality and editorial production in their separate epics.

Acceptance criteria:

• Field-level models cover all eight website content types.
• Frontmatter contracts distinguish website content from operational Markdown.
• Validation, migration and content-loading boundaries are documented.
• Child deliverables are verified without duplicating module or editorial work.

Unanswered clarification questions

These questions clarify content-foundation coordination without approving new models, publication scope or implementation.

1. Which source inventory and field-level models are authoritative for the eight website content types?
2. Which Markdown profiles are operational rather than website content, and how should that distinction be recorded?
3. What approved contracts separate schema definition, executable validation, migration and content loading?
4. Which existing child outcomes provide acceptance evidence for each foundation deliverable?
5. Who reviews the shared contracts and confirms that cross-module dependencies and unresolved decisions are recorded?