Define and validate Comic Manifest rendition and publication requirements #94

Parent epic: #6

Summary

Define and validate Comic Manifest rendition and publication requirements for Comic Manifest v1.

Ownership and dependencies

• Repositories: codex and platform.
• Depends on: Implement Comic Manifest episode and panel structure #91, Implement Comic Manifest immutable dependency and asset references #92.
• Plan position: 7 of 12.

Scope and deliverables

• Specify required output renditions and explicit profile versions, dimensions, media types and applicable limits.
• Define accessibility descriptions, Studio credit, rights notices and publication metadata requirements.
• Implement validation and compatibility checks against declared outputs and episode identity.
• Document that declarations do not prove rights ownership, creative quality or rendering correctness.

Acceptance criteria

• Synthetic output profiles validate and incompatible/missing requirements fail.
• Accessibility, credits and rights requirements are explicit and tested.
• Rendition requirements identify outputs without implementing rendering, lettering or distribution.
• Normative additions are reviewed in Codex before Platform adoption.

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.