happier-release-notes

# Happier Release Notes This skill owns only source-coupled release-note mechanics: the canonical changelog section schema, bounded-channel projection, StoryDeck cards, translations, assets, and generation. It does not choose release scope, group changes, write editorial prose, recommend patch/minor/major, approve content, or dispatch a release. For those decisions, start with the private maintainer release authority: ```bash hmaint release bootstrap --repo <absolute checkout> --json ``` ## Read first 1. Read `apps/ui/release-notes/README.md` and `apps/ui/release-notes/releases/README.md`. 2. Inspect `apps/ui/sources/changelog/releaseNotes/types.ts` and `apps/ui/sources/components/ui/storyDeck/storyDeckCardLimits.ts` before changing card data or limits. 3. If UI behavior changes, use the canonical UI testkit and TDD. ## Canonical changelog and bounded projections `apps/ui/CHANGELOG.md` is the single authored authority for one release's public Markdown and exact bounded channel text. Put this JSON comment at the start of the matching `## Release <project-release-id> - <date>` section. The project release ID is a unique lowercase identifier such as `2026-08-09.1`, independent of every component version. Use the date plus an ordinal, increase the ordinal for another candidate on that date, and keep the same ID from preview through stable. The heading is the only authored source; a workflow input only selects and verifies it: ```markdown <!-- happier-release-note...