happier-release-promote

# Happier Release Promote Use this skill only after `happier-release-validation-review` approves the candidate. ## Mission Perform the actual release promotion through the canonical repo release orchestrator. This skill has external side effects and must always ask for explicit human approval before the non-dry-run command. ## Required Inputs - Human approval from validation review - Target lane: preview or production - Candidate branch/worktree - Bump mode - Deploy targets - Mobile/desktop action choices, if any ## Process 1. Re-read `AGENTS.md`. 2. Read `references/promotion-commands.md`. 3. Confirm validation review verdict is `APPROVE_FOR_PREVIEW_PROMOTION` or equivalent production approval. 4. Run dry-run command. 5. Summarize planned side effects. 6. Ask for explicit approval to run the real command. 7. Execute only after approval. 8. Monitor GitHub/release jobs until completion. 9. Verify the post-publish `release-verify.yml` result when the release profile triggers it, or explicitly record why it was skipped. 10. Report published versions/artifacts and any follow-up verification. Never bypass `node scripts/pipeline/run.mjs release` for full releases unless the user explicitly requests a manual partial publish. ## Target Discipline Preview and production have different gates. Use this skill with an explicit target: - `preview`: promote `dev` to `preview` after validation review approval. - `production`: promote `preview` to `main` only after preview soak and ...