releaselisted

# release Release preparation, validation, and publishing. ## Routes | Subcommand | Action | | ---------- | ------ | | `prep` | Release readiness checks | | `security` | Pre-release security audit | | `health` | Code health check | | `audit` | Release-audit stage — what class of defect could this release introduce? | | `publish` | Version bump and publish | ## Usage ```bash /release # Ask what to do /release prep # Release prep checks /release security # Security audit /release health # Health check /release audit # Release-audit stage (packet + sitting) /release publish # Publish release ``` ## Behavior ### prep Run release preparation workflow: ```bash uv run attune workflow run release-prep ``` This checks: - Test suite passes - No critical security issues - Documentation is current - Changelog is updated ### security Run security audit focused on release readiness: ```bash uv run attune workflow run security-audit --path src/ ``` ### health Run code health checks: - Test coverage - Lint status - Type check status - Dependency audit ### audit The release-audit stage (`docs/specs/release-audit-stage/`). The other release surfaces check hygiene; this one asks what class of defect THIS diff could have introduced. It sits every release (D2) — an empty residual still sits, which is cheap by design. ```bash python -m attune.classes.stage --repo <owner/name> ``` Six steps: baseline (merge-base vs the last