releaselisted

# Release ## Iron Law `BREAKING CHANGES BUMP MAJOR. AGENTS PREPARE RELEASES; HUMANS MUTATE SHARED ENVIRONMENTS.` ## When to Use - The user asks for release prep, versioning, changelog, release notes, tags, publish planning, rollout, rollback, deprecation, or migration notes. - The user approves release prep after a concrete diff exposes release artifacts or rollout obligations. - A repo validator requires release artifact sync for an approved change. ## When NOT to Use - Starting release work because a change might later need it. Note the risk in `workflow` and ask at the concrete release-prep decision point. - Triggering deploys, rollbacks, promotions, production config, flag flips, DNS, or infrastructure applies. Prepare the command or checklist for a human. - Database DDL safety; pair with `database`. Local bootstrap; use `scaffolding`. ## Rules 1. Release is a late gate. Implementation approval is not release approval. 2. Agents prepare evidence, notes, checks, runbooks, and command plans. Humans run anything that mutates a shared environment, including staging config and feature flags. Report agent-run checks and human-run commands separately. 3. Classify per release unit. In a monorepo, each library, CLI, plugin manifest, or container may have its own stream; lockstep bumps need repo policy or user approval. Use the higher plausible bump when compatibility is unclear. 4. Release artifacts move together: manifests, committed lockfile