[irzhywau]

Note

This is part of a stacked PR chain — review only the commits of this checkpoint; earlier work is in the PRs below it in the stack.

Stack (top → bottom)

• feat(protected-content): runtime lifecycle — mint, buy, play, purchase closeout #36 feat/protected-content-runtime-lifecycle
• feat(protected-content): chain rights evidence and typed decisions #35 feat/protected-content-rights
• feat(protected-content): Runtime release authority and persisted state #34 feat/protected-content-runtime
• feat(protected-content): sign rights requests with Wallet #33 feat/protected-content-wallet-rights
• feat(protected-content): custody provider protocol and process #32 feat/protected-content-custody-provider
• ➡️ feat(protected-content): bridge authenticated release reconstruction #31 feat/protected-content-key-reconstruction (this PR)
• feat(protected-content): threshold custody envelopes and key reconstruction #30 feat/protected-content-custody
• feat(protected-content): canonical content identities, rights grants, release contracts #29 feat/protected-content-contracts
• feat(collaboration): Profile/Chat product UI and Home window chrome #28 review/collaboration-product-integration
• feat(collaboration): signed network protocol, Carrier transport, Profile authority #27 review/collaboration-foundation
• main

Base: feat/protected-content-custody ← Head: feat/protected-content-key-reconstruction (checkpoint 5 of 10)

Commits

• a8d0a9a feat(protected-content): bridge authenticated release reconstruction

[irzhywau]

One commit was added on top of a8d0a9a6: 467a6c03, the merge of the updated parent feat/protected-content-custody (checkpoint 4 tip, CI-green — strict statement-signature verification and the checkpoint 3 fixes below it). No fixes were needed on this checkpoint itself.

Review notes: the bridge from VerifiedKeyReleaseRequestV1 to AuthenticatedRuntimeReleaseOperationV1 preserves the reconstruction check order exactly (envelope identity → recipient → exact threshold → per-node verify/dedupe → terminal receipt → Released outcome → open → combine → constant-time commitment), the old request-based entry correctly drops to #[cfg(test)], and the 12 new tests mirror the prior edge cases through the new path.

Two observations carried from the checkpoint 4 review that become slightly more relevant here (no code changed): (a) verify_node_contribution/verify_terminal_receipt re-verify the operation statement but not the operation's own issued/expires window — safe via the current sole caller, but the new public reconstruction entry now leans on that invariant; (b) expected_terminal_issuer stays caller-supplied, and the new happy-path test passes the receipt's own issuer (circular for that test; wrong-issuer negatives from checkpoint 4 still cover it).

Verified locally at the tip: all source gates incl. the provisional-retirement guard, cargo fmt --check, cargo clippy --workspace --all-targets -- -D warnings, cargo test --workspace — 2090 passed (only the known macOS mDNS-environment room::direct pair plus one under-load-only wallet-timeout flake, all green on this CI run).