cc-cream 0.1.9 → 0.1.11

package/CHANGELOG.md

@@ -4,6 +4,16 @@ All notable changes to cc-cream are documented here. Format follows
 [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); versions follow
 [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.1.11] — 2026-05-29
+
+### Fixed
+- **Status bar could pin to an old version when a non-semver cache dir exists** (CREAM-kxwhbwzq). The plugin-mode statusLine self-resolves the highest installed version with `ls -1d …/cc-cream/*/ | sort -V | tail -1`. `sort -V` sorts directory *names*, so a git-sha install dir (e.g. `c83650b6360f/`) sorts after every `0.1.x` and got picked — pinning the bar to whatever version that dir held (observed: 0.1.3), with `/plugin update` unable to move off it. The command now filters to semver-named dirs (`grep -E '/[0-9]+(\.[0-9]+)+/$'`) before `sort -V`, so a stray non-numeric dir can't hijack version selection. Re-run `/cc-cream:setup` once (or reinstall) to rewrite the statusLine with the hardened command.
+
+## [0.1.10] — 2026-05-29
+
+### Added
+- **Setup reminder after plugin install** (CREAM-cpcwjkxi). Installing the plugin makes the commands available but can't wire the status bar (Claude Code has no install hook to write `settings.json`), so users saw no bar and didn't know to run `/cc-cream:setup`. A `SessionStart` hook (`hooks/hooks.json`, auto-discovered) now emits a one-line `systemMessage` nudging the user to run `/cc-cream:setup` — but **only while cc-cream's statusLine is absent**, so it self-silences once setup runs. `systemMessage` is shown to the user and adds **nothing** to the model context (zero tokens). Degrades safely: missing `settings.json` → nudge; malformed → silent; always exits 0. Biome now also lints `hooks/`.
+
 ## [0.1.9] — 2026-05-29
 
 ### Fixed

package/README.md

@@ -72,9 +72,10 @@ Then wire it into your settings in one step:
 ```
 
 The `/cc-cream:setup` command runs the consent installer, which writes the
-`statusLine` block to `~/.claude/settings.json`. Updates are automatic: when
-`/plugin update` drops a new version into the cache, the next render picks it
-up without any further action.
+`statusLine` block to `~/.claude/settings.json`. Until you run it, cc-cream
+prints a one-line reminder at the start of each session (it stops once the bar
+is wired). Updates are automatic: when `/plugin update` drops a new version into
+the cache, the next render picks it up without any further action.
 
 ### Option 2 — npm
 

package/package.json

@@ -1,12 +1,12 @@
 {
   "name": "cc-cream",
-  "version": "0.1.9",
+  "version": "0.1.11",
   "description": "Claude Code cache/context/cost status-line tool",
   "directories": {
     "doc": "docs"
   },
   "scripts": {
-    "lint": "biome lint src/",
+    "lint": "biome lint src/ hooks/",
     "knip": "knip",
     "validate": "command -v claude >/dev/null 2>&1 && claude plugin validate . || echo 'cc-cream: claude CLI not found — skipping plugin validation'",
     "pretest": "npm run lint && npm run knip && npm run validate",

package/src/install.js

@@ -23,10 +23,13 @@ const TRUST_NOTE =
 // `nodePath` is the ABSOLUTE node binary, resolved once at setup time — the
 // statusLine subprocess may not inherit the user's PATH, so a bare `node` is
 // unsafe. The `-d .../*/` glob yields directory paths with a trailing slash, so
-// `src/cc-cream.js` concatenates directly. `sort -V | tail -1` picks the highest
-// installed version, so `/plugin update` is applied live with no re-run of setup.
+// `src/cc-cream.js` concatenates directly. The `grep` keeps ONLY semver-named
+// dirs (e.g. `0.1.10/`) before `sort -V | tail -1` picks the highest — without
+// it, a non-numeric cache dir (a git-sha install like `c83650b6360f/`) sorts
+// last and pins the bar to whatever version that happens to be, defeating
+// auto-update. With it, `/plugin update` is applied live with no re-run of setup.
 export function autoUpdateCommand(nodePath) {
-  return `${nodePath} "$(ls -1d "\${CLAUDE_CONFIG_DIR:-$HOME/.claude}"/plugins/cache/*/cc-cream/*/ 2>/dev/null | sort -V | tail -1)src/cc-cream.js"`;
+  return `${nodePath} "$(ls -1d "\${CLAUDE_CONFIG_DIR:-$HOME/.claude}"/plugins/cache/*/cc-cream/*/ 2>/dev/null | grep -E '/[0-9]+(\\.[0-9]+)+/$' | sort -V | tail -1)src/cc-cream.js"`;
 }
 
 // `desired` is considered already installed if it matches the planned command