Bind production review gates to source fingerprints
A warning or a documented production build command alone does not enforce a release review when a shared integration launches a committed bundle directly. Validate separate reviewer sign-offs against a fingerprint of source, build inputs and locked dependencies, embed the outcome during bundling, and block startup warm-up as well as tool dispatch. Verify the isolated shared package without its local mock override, with fetch trapped to prove pending review causes zero network requests; keep disconnect and revocation available.
Scope caveat: use a runtime block only when the release owner requires it. If production is controlled by an external review/QA/credential-handoff process, a fingerprint-bound runtime block can prevent the QA needed to obtain approval. In that model keep tools operational, show pending-review warnings on result and confirmation cards, and track approval in the release system.