releaselisted

# Release Prepare feature work for a future release or publish an actual release through one explicit Release Contract, with exact state, side effects, artifact-sidecar handling, and cleanup candidates named before action. ## Arguments - `$ARGUMENTS` — Optional version, release type (`patch`, `minor`, `major`), feature branch/name, or mode: `prepare-only` / `publish`. ## Always - Use one approval gate per release attempt: **Release Contract Approval**. - Always present the exact Release Contract before the first side effect. - Skip only the approval prompt when the current turn unambiguously approves the full normal lifecycle and all release targets are known. - Current-turn approval never implies remote feature-branch or sidecar deletion unless the exact remote ref deletion is listed in the Release Contract. - Default cleanup disposition is delete/remove for every eligible feature code worktree, local feature branch, remote feature branch, and artifact sidecar worktree/ref after final base/target push sync. - Keep cleanup candidates only for a hard blocker (dirty worktree, failed ancestry/inclusion, active review/audit/package need, missing final sidecar checkpoint, checked-out branch without removable worktree, unverifiable remote state) or explicit user keep request. - The approved contract covers only listed file edits, feature merge, commits, pushes, tag/GitHub release actions, and cleanup candidates. - `prepare-only` is feature integration: merge to the bas