releaselisted

# Release Promote one pinned, user-accepted artifact to an authorised target. This skill owns the authority gate and evidence; runbooks and tools own mechanics. ## Entry gate Require accepted delivery receipt, exact accepted-artifact `digest|git_revision`, typed action (`deploy`, `publish`, `share`, `send` or `activate`), target-bound release authority, owner, disclosure/data policy and project instructions. Implementation acceptance is not promotion authority. Broad project/session authority cannot release or deploy; the promotion grant must bind this artifact, action, target, expiry and applicable constraints. Start from canonical [RELEASE.template.json](templates/RELEASE.template.json). The validator accepts only that typed receipt and fails closed on every other shape. ## Readiness Record and verify: - action, target ID/kind, provider-independent tier and disclosure boundary; - authority covering the target, artifact, operations, expiry, secrets, communication, public disclosure and irreversibility; - state/data impact: ordered steps, compatibility window and purpose-typed evidence bound to passing checks; - bounded promotion plan, exposure cap and stop conditions; - realistic rollback, revocation, recall, deactivation, replacement or containment plan, with owner and time bound; - proof requirements, evidence source, owner, close condition and observation window when outcome needs time; - recipient/audience validation, retention and required communications.