[soulbah]

Spec and outcome

• Spec or repository-only rationale: Promotion of validated dev into main under docs/adr/007-promoted-releases-and-major-tags.md. The range contains ci(release): move the major tag only to an immutable release #26, which entered dev through a pull request gated by quality.
• Accepted outcome: main fast-forwards from 170bde7 to 8aab4ce (1 commit, ci(release): move the major tag only to an immutable release #26) once quality passes on this exact head, so the next release run from main moves the major tag only to an immutable release. The promotion publishes no release and moves no tag.
• Explicit non-goals: No release, no version or major tag change, no published release integration as part of this pull request.

Done when and evidence

• Done when command or protocol: quality passes on this head; then gh workflow run promote.yml --ref dev -f pull_request=<this number> fast-forwards main and no workflow starts from the push.
• Evidence path or exact output: Range 170bde7..8aab4ce matches dev; main is its ancestor. ci(release): move the major tag only to an immutable release #26 passed quality on its head.
• Full gate: bun run verify

Risk and privacy

• Security/privacy impact: main receives the immutability requirement before any release can run from it; nothing publishes on push.
• Offline and determinism impact: None.
• Dependency or toolchain change: None.
• Rollback path: Close this pull request before promotion. After promotion, revert on dev and promote again; main never rewinds.

Review checklist

• Scope matches accepted spec or repository-only rationale.
• Success, boundary, failure, and regression paths have evidence proportional to risk.
• No secret, real Terraform material, private AI material, or generated noise enters Git.
• Primary reviewer inspected final diff and recorded remaining limits.