tenet-release-opslisted

# Tenet Release Operations Audits whether changes can be shipped, observed, and rolled back safely. This complements `tenet-build-ci` by focusing on production release mechanics after CI turns green. ## Language Support Matrix ```yaml support: native: [yaml, json, markdown, dockerfile, shell] heuristic: [typescript, javascript, python, go, ruby, java] ``` ## Procedure ### Step 0: Detect Applicability Applicable when the project appears deployable: Dockerfile, deployment workflow, package publish config, server entrypoint, infrastructure config, or release docs. If the repo is a small library with no deployment/publish path, write `score: null`, `applicable: false`. ### Step 1: Deployment Strategy Check deployment workflows and docs for: - manual deploys with no checklist - direct deploy to production from local machine - no environment promotion path - no smoke test after deploy Severity: - `critical`: production deploy bypasses CI or uses unreviewed local state - `major`: no smoke test, promotion, or release gate for deployable app - `minor`: deploy flow exists but docs are stale or incomplete ### Step 2: Rollback and Recovery Search for rollback commands, image tags, database rollback notes, release runbooks, and incident procedures. Severity: - `critical`: no rollback path for production deploys with migrations or external state - `major`: rollback exists for app code but not database/config/state - `minor`: rollback doc exists but lacks owner, expected du