Define versioned Comic Manifest contracts and fixtures #89

Parent epic: #6

Summary

Define versioned Comic Manifest contracts and fixtures for Comic Manifest v1.

Ownership and dependencies

• Repositories: codex; platform consumer proof.
• Depends on: Define Comic Manifest architecture and boundaries #88.
• Plan position: 2 of 12.

Scope and deliverables

• Create normative specifications, versioned schemas and an RFC for production, build-result and public release records.
• Specify canonical identities, references, classifications, exact-version support, unknown-field behavior and relational invariants.
• Include valid/invalid public synthetic fixtures for episode structure, outputs, revision/approval linkage and private-context projections.
• Identify semantics that require runtime validation rather than claiming schema validity proves authorization.

Acceptance criteria

• All record kinds have closed, versioned schemas and human-readable semantics.
• Positive and negative fixtures cover both schema and cross-record relationships.
• Compatibility, migration/deprecation and release boundaries are documented.
• Released Prompt SDK, Context Package and Context Builder contract bytes remain unchanged.

Implementation guardrails

Follow Constitution v1.0.0 at a9cc8a503aa30e17820edc62ac95f7cbe10e0564 and the boundaries in #6. Use public/synthetic fixtures only. Preserve released Prompt SDK v1, Context Package v1 and Context Builder v1 bytes. Add focused tests and documentation with implementation; the suite task consolidates rather than postpones testing. No implicit retrieval, permission renewal, direct Lore checkout, silent declassification, self-approval or canon promotion. Normative gaps belong in Codex. Orchestration, rendering, production trust onboarding and creative canon remain separately scoped. Creating this issue does not authorize implementation or publication.