Create Comic Manifest conformance and security reference suite #98

Parent epic: #6

Summary

Create Comic Manifest conformance and security reference suite for Comic Manifest v1.

Ownership and dependencies

• Repositories: platform; codex synthetic conformance fixtures.
• Depends on: Create Comic Manifest authoring CLI and Epic 7 reference consumer #97.
• Plan position: 11 of 12.

Scope and deliverables

• Consolidate parsing, semantics, identities, references, SDK/Builder integration, outputs, approvals, projections and CLI coverage.
• Add reviewed golden scenarios for public and fake-private comics, revisions/corrections, incomplete results and deterministic processing.
• Cover hostile text, malformed JSON, traversal, tampering, unauthorized reads, stale/revoked approvals and redaction.
• Provide reusable offline fake-adapter tests and supported Node CI with an explicit positive/negative coverage map.

Acceptance criteria

• Every core contract/security boundary has positive and negative coverage.
• Goldens require explicit owner review and are never rewritten by tests.
• CI and full reference flows need no paid providers, secrets or actual private content.
• Tests document deterministic guarantees without claiming uncontrolled generated art is bit-for-bit reproducible.

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.