happier-release-validation

# Happier Release Validation Use this skill when asked to validate a Happier release candidate such as `v0.2.6` before promoting `dev` to `preview`. ## Mission Validate the current development release lane end-to-end before preview promotion, with special focus on user upgrade safety: installations, daemon ownership, background services, daemon-server auth, session creation, session continuity, provider launches, web UI, native mobile, server, CLI, and release artifacts. This skill may create branches/worktrees, run local checks, run VM/host QA, and implement root-cause fixes. It must not publish, promote, submit mobile builds, or trigger production/preview release side effects. Candidate validation must use local candidate artifacts. It may install the currently published `preview` release only to create a realistic before-upgrade baseline; after that, upgrades and installer/artifact checks must use locally built artifacts from the validation worktree, `--source local-build --ref .`, or an explicitly recorded local artifact transfer to the target machine. ## Start 1. Re-read `AGENTS.md` and `docs/release-process.md`. 2. Read `references/workflow.md` for the orchestration loop and human gates. 3. Read `references/lane-catalog.md` for current lanes and commands. 4. Read `references/manual-qa-matrix.md` before any OS QA lane. 5. Read `references/daemon-ownership-scenarios.md` before lane L21. 6. During Phase 0, read the prior battle-tested release-readiness run at `.proj...