Release Stamp Afteruse Review

The review opens from visible state pressure, not a timer. Required branch families:

• certify_release_scope - keep the release stamp but state exactly who can cite it;
• restrict_release_afteruse_reader - block the later reader from treating the stamp as universal release;
• attach_facility_or_public_bridge - spend facility route proof, public restitution, lawful seal, checksum, or route asset bridge to make the use accountable;
• reopen_locked_target_or_claimant - bring the source target, recovery-only lock, or harmed claimant back into the route surface;
• split_release_stamp_afteruse - preserve the release while splitting afteruse into separate reader-bound receipts;
• quarantine_release_stamp_afteruse - lock the stamp until missing proof, route state, claimant answer, or scope bridge is produced;
• false_release_stamp_afteruse_default - default branch if the player accepts false-clean release stamp afteruse;
• future_effect_any - every branch mutates a future reader, route, counter, target, room, or claimant posture.

All non-default relief must carry at least one cost and one future route effect.