public-release-gatelisted

# Public Release Gate Treat a Release as a separate deliverable. Repository commit checks do not constitute a Release review; inspect the source, final artifacts, release page, and deployment state together. The sibling `public-repo-git-gate` skill owns the public-content and branch gates for commit, push, and PR operations. Do not repeat this skill's artifact checks for an ordinary commit. This skill is a manual review workflow. A passing script or CI job alone does not prove every Release condition. Reuse the project's existing automated checks first, then manually verify final artifacts, the hosting platform, and production. Mark the gate as passed only when the required evidence exists. Keep the review read-only by default. Creating a tag or GitHub Release, uploading attachments, changing production configuration, or deploying each requires explicit user authorization. Passing this gate does not authorize any of those actions. ## Inputs and output Before starting, identify the repository root, target version and tag, final artifact paths, third-party resource inventory, production URL, and project-specific configuration. Return a structured record containing at least: ```text Release gate: PASS | BLOCKED | FAILED Repository: Version / tag: Build and artifacts: Publicity and sensitive-data scan: Third-party notices: Deployment and response headers: Release page and attachments: Evidence: Skipped checks / residual risks: ``` `PASS` means that all required evidence w