Compile job, revision, preflight, approvals, QA and vendor data into a local release packet with a hold/review/ready decision.
A release packet should answer one question: what evidence supported the decision to send this revision into production? The center therefore collects the current Job Core record, preflight state, approvals, QA and supplier decision instead of asking the operator to retype them into a separate form.
If a mandatory gate is missing, the packet stays REVIEW. If a saved gate explicitly contains a blocking state, the packet becomes HOLD. Only a complete set of acceptable required evidence can produce READY, and the generated JSON records the same decision rather than exporting a cosmetically clean summary.
Store the packet beside the production files or ticket number used for the job. The packet does not include image bytes, so it should be treated as a decision manifest that points to the authoritative production assets.
The center deliberately refuses a clean READY state when a required gate is missing or explicitly blocked.
The downloadable packet records what the browser knew; it does not convert a planning result into a contractual production approval.
The current revision identifier is included so a release packet cannot be mistaken for evidence about a later file.