Integrate Comic Manifest with Context Builder and Prompt SDK references #93

Parent epic: #6

Summary

Integrate Comic Manifest with Context Builder and Prompt SDK references for Comic Manifest v1.

Ownership and dependencies

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

Scope and deliverables

• Validate manifest bindings to exact reviewed prompt definitions, declared context slots and prepared package instances.
• Reuse the released Builder/SDK boundaries and preserve protected evidence links without extending their immutable schemas.
• Require independently supplied current authorization at use boundaries; historical approvals and provenance are not reusable grants.
• Demonstrate integration with public synthetic inputs and offline mock consumers, not production orchestration.

Acceptance criteria

• An exact valid manifest/prompt/package combination passes the reference handoff.
• Wrong prompt, package, purpose, slots, classification or stale/revoked authorization fails before prohibited effects.
• Manifest validation does not implicitly refresh sources, renew permission or invoke a model.
• Existing released SDK and Builder conformance remains passing.

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.