Implement Comic Manifest revision and approval boundaries #95

Parent epic: #6

Summary

Implement Comic Manifest revision and approval boundaries for Comic Manifest v1.

Ownership and dependencies

• Repositories: platform; codex lifecycle semantics.
• Depends on: Integrate Comic Manifest with Context Builder and Prompt SDK references #93, Define and validate Comic Manifest rendition and publication requirements #94.
• Plan position: 8 of 12.

Scope and deliverables

• Implement immutable revision identities, predecessor/correction relationships and deterministic meaningful diffs.
• Bind independently verified approval to exact content/artifact identities, scope and intended action.
• Reject affected approvals after edits, expiry or revocation; distinguish review from publication/canon authority.
• Support explicit offline approval fakes without presenting them as production trust infrastructure.

Acceptance criteria

• Unchanged approved revisions pass their scoped checks; modified or mismatched revisions do not inherit approval.
• Stale/revoked/unknown approvals and caller-supplied status strings cannot authorize transitions.
• Correction/revision tests preserve episode identity and immutable history.
• Diffs and diagnostics obey classification and disclosure policy.

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.