release-coordination

Release Coordination（生产发版协调）

Use this as the production release coordinator for scope confirmation, production MR, merge authorization, tag/build gate, evidence closeout, or reset.

Skip / route directly when the task is narrower:

• Release / launch document substance → release-doc-writer.
• Rollout/canary/rollback/control plane → platform-release-engineering.
• Risk gates → feature-risk-router.
• Verification strategy → testing-strategy.
• Active post-release error → defect-diagnosis.
• Wording polish → tighten-doc.

This skill coordinates gates; it does not itself authorize merge, tag push, production mutation, manual job play, force-push reset, or destructive cleanup. Boundary: once the user authorizes a merge, post-merge closeout cleanup of the merged temporary feature branch created for this delivery (worktree + local branch + remote branch) is already covered by that merge authorization per worktree-isolation 收尾 — do not re-ask (eligibility evidence per the Authorization matrix cleanup row). Permanent/integration source branches (e.g. dev) are never cleaned up under this carve-out, and an unclear branch role means preserve and ask; cleanup mechanics and safety rails stay with worktree-isolation.

Owner routing

Concern	Owner
Release document evidence	release-doc-writer
Rollout / rollback / production control plane	platform-release-engineering
Risk labels and mandatory gates	feature-risk-router
Verification strategy	testing-strategy
Active incident / failed smoke	defect-diagnosis
Release evidence signals	platform-observability
Local branch/worktree safety	worktree-isolation
MR/CI/tag commands	repo tooling (glab, gh, approved API/CLI)
Feishu/Lark document operations	Feishu/Lark tooling
Wording polish	tighten-doc

Core lifecycle

1. Intake — stated scope, production target, release source, tag rule, doc artifact, environments, and user decisions.
2. Scope-confirmation gate — compare intended scope with first-hand base...release-head diff/log evidence; block on mismatch, over-broad source, target drift, or undocumented operational deltas.
3. Test-scope prompt — emit test-scope handoff from confirmed diff; route full design to testing-strategy.
4. Release-doc gate — invoke release-doc-writer to write confirmed scope/evidence depth before MR/merge authorization.
5. MR/PR gate — duplicate check; read back URL, source/target, head SHA, CI, mergeability, discussions, auto-merge, and the remove-source-branch flag (the flag may stay set only if the cleanup row's source-eligibility conditions — temp branch created for this delivery, no other open or plan-declared consumer — still hold at merge time; otherwise read the flag back OFF before merging — asking may resolve classification, never waive this invariant).
6. Merge gate — re-read immediately. A user-requested release includes its necessary in-scope merges; repairs/new PRs refresh validation, not permission. Single-object and explicit counted-batch directives keep their limits. Resolve foreign/out-of-scope changes before acting (canonical: references/mr-merge-authorization.md + worktree-isolation 合并执行协议).
7. Tag/pipeline gate — verify tag absence/target; after push read back remote tag and pipeline/job behavior.
8. Rollout/config handoff — live mutation goes to platform-release-engineering; this skill tracks evidence.
9. Watchers — bounded read-only watchers; stop on terminal/manual/timeout and reconcile.
10. Closeout — report only read-back facts and explicit gaps/deferred items.
11. Post-release reset — remote ref maintenance with dry-run/before-after SHAs, --force-with-lease, and SHA equality proof.