releaselisted

Release and deploy very-happy: publish the very-happy-cli npm package from v* tags, deploy happy-web-v2 and happy-server to the active production host, update the mac-office daemon, verify production, and roll back. Use when asked to release, publish, deploy, ship, roll back, or update production.
Mereithhh/very-happy · ★ 5 · AI & Automation · score 70

Install: claude install-skill Mereithhh/very-happy

# very-happy release Production is `veryhappy.dev`: server + Web V2 on vh-sg (AWS Singapore), published CLI on npm, daemon on mac-office. `docs/operations.md` is the topology/runbook source; `docs/PROCESS.md` is the gate/process source. The only canonical source and release repository is the public GitHub repository `Mereithhh/very-happy`. A private archive is read-only history: never push a release commit or tag to it, and never trigger a deployment from it. ## Establish the target Release targets are: - `server`: publish and deploy the complete server image, including Web V2. - `web`: deploy the same complete image; Web is not a host-mounted artifact. - `cli`: publish `very-happy-cli` from a `vX.Y.Z` tag. - `daemon`: install the published CLI and restart mac-office via `vh-update`. - `all`: normally server → web → CLI → daemon, modified only by a spec's compatibility matrix. Before any external mutation, show the intended commit/version, dirty-worktree state, target and rollback point. Do not deploy unrelated local edits. ## Mandatory preflight ```bash git status --short git branch --show-current git log -1 --oneline RELEASE_ORIGIN=$(git remote get-url origin) case "$RELEASE_ORIGIN" in https://github.com/Mereithhh/very-happy.git|git@github.com:Mereithhh/very-happy.git) ;; *) echo "refusing release from non-canonical origin: $RELEASE_ORIGIN" >&2; exit 1 ;; esac test "$(gh repo view Mereithhh/very-happy --json visibility --jq .visibility)" = PUBLIC ``` Run the