| name | sea-release |
| description | Canonical SEA-Forge release workflow for release preparation, validation, branch promotion, tagging, rollback, and release-gate evidence. Use when preparing a release, promoting dev to stage or stage to main, cutting a version tag, validating release readiness, handling hotfix forward-merges, planning rollback, or executing a full end-to-end release. Prefer existing just recipes and evidence-producing gates over ad hoc deployment steps. |
| disable-model-invocation | true |
SEA Release
Run the repository's canonical release flow using existing just recipes, release gates, and evidence artifacts.
When To Use
Use when the user asks to:
- prepare a release
- validate release readiness
- promote
dev to stage
- promote
stage to main
- cut a release tag
- handle a hotfix release and forward-merge it back
- plan rollback
- run the full release end to end
Do not invent Docker, Kubernetes, registry, or package-publish steps.
Modes
- Default mode: run checks autonomously, but stop before irreversible or production-sensitive actions.
e2e mode: if the release request includes the exact keyword e2e, treat that as one-time approval for the canonical end-to-end release flow, including promotions and tagging.- Inferred autonomy: if the request implies a full autonomous release but does not include
e2e, ask for confirmation by telling the user to reply with e2e.
Core Rules
- Prefer
just recipes and existing repo scripts.
- Treat
just ci as the CI-parity check.
- Treat
just enterprise-governance-gate as the release-gate entrypoint.
- Use promotion recipes instead of manual merges when a recipe exists.
- Do not claim
release-gate-proof or enterprise-shippable without executed validation and an evidence artifact.
Load Only What You Need
- references/workflow.md: scope selection,
e2e trigger behavior, preflight checks, promotion order, tag flow, rollback posture, and output shape.
Quick Reference
just ci-quick
just ci
just enterprise-governance-gate
just promote-stage
just promote-main
just release <version>
just hotfix-forward
Stop And Ask
Stop if the task would require:
- destructive recovery or rollback
- deleting or rewriting tags
- acting on ambiguous branch, version, or release scope
- claiming release readiness without executed proof
If autonomy is implied but e2e is absent, ask the user to confirm by replying with e2e.
