@groeponline/pi-wishcraft 1.4.15 → 1.4.16

package/AGENTS.md

@@ -118,6 +118,12 @@ CI workflows (`.github/workflows/`):
 - `release.yml` — reuses test.yml, prepares release-candidate branch
 - `promote-release-candidate.yml` — promotes verified SHA to main, tags, dispatches publish
 
+Release behavior:
+- **Every main merge with `[Unreleased]` CHANGELOG notes cuts a release automatically** (verify → candidate → promote → tag → npm). Notes-less merges skip candidate creation entirely — no more empty versions.
+- Notes live under `## [Unreleased]` in CHANGELOG.md; the release commit rolls them into the new version heading.
+- `[skip release]` skips the release when it appears in the **commit subject** — squash-merge builds that subject from the commit subject lines, so a `[skip release]` in a PR title is NOT preserved. Careful: the guard substring-matches the whole commit message, so don't write the literal tag in prose either.
+- Manual escape hatch: `node scripts/release.mjs <version> --force` cuts a release with empty notes (deliberate, local only).
+
 ## Code Conventions & Common Patterns
 
 ### Module Structure

package/CHANGELOG.md

@@ -2,6 +2,11 @@
 
 ## [Unreleased]
 
+## [1.4.16] - 2026-09-05
+
+### Fixed
+- Release pipeline no longer cuts empty releases: candidate preparation (and the local `release` script, behind `--force`) now requires actual `[Unreleased]` notes in the CHANGELOG before bumping, so notes-only and docs-only merges to main no longer publish versions with empty release sections.
+
 ## [1.4.15] - 2026-09-05
 
 ### Added

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@groeponline/pi-wishcraft",
-  "version": "1.4.15",
+  "version": "1.4.16",
   "description": "Operator cockpit for Pi: live powerline status, searchable skills, idea queue, sticky Bash, hooks, policy controls, and session UX.",
   "type": "module",
   "files": [