Implement strict Comic Manifest parsing and semantic validation #90

Parent epic: #6

Summary

Implement strict Comic Manifest parsing and semantic validation for Comic Manifest v1.

Ownership and dependencies

• Repositories: platform.
• Depends on: Define versioned Comic Manifest contracts and fixtures #89.
• Plan position: 3 of 12.

Scope and deliverables

• Implement bounded raw JSON parsing with duplicate-key, Unicode, depth and resource-limit checks.
• Adopt exact reviewed Codex references and reproducibly generate validators using locked dependencies.
• Add closed-field, version, identity and semantic validation with value-free diagnostics.
• Keep validation separate from source retrieval, execution, approval and publication.

Acceptance criteria

• Valid fixtures pass; malformed, duplicate-key, oversized, unknown-field and unsupported-version inputs fail deterministically.
• Parsing/validation performs no implicit network calls, source reads or execution.
• Diagnostics do not disclose protected values or raw exceptions.
• Focused tests and public API documentation accompany implementation.

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.