cc-cream 0.1.14 → 0.1.16

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.16] — 2026-05-29
+
+### Fixed
+- **The status bar silently rendered nothing when `~/.claude` is a symlink** (dotfile managers like stow/chezmoi/yadm, or an iCloud/Dropbox-synced config dir). The "am-I-the-entrypoint" guard compared `import.meta.url` (which Node's ESM loader canonicalizes — symlinks resolved) against `pathToFileURL(process.argv[1])` (left as-invoked, through the symlink). Under a symlinked path the two never matched, so `main()` never ran and the bar appeared as an empty line with no error — invisible to diagnose. The guard now compares **realpaths** (falling back to the href check if realpath fails), so a symlinked install renders correctly. Found while verifying a fresh v0.1.15 plugin install.
+
+## [0.1.15] — 2026-05-29
+
+### Fixed
+- **An orphaned status line no longer crashes on every render after `/plugin uninstall`.** If you ran `/plugin uninstall cc-cream` without first running `/cc-cream:uninstall`, the `statusLine` entry stayed in `settings.json` while the plugin cache was deleted. The cache-glob then matched nothing, the baked command collapsed to a bare relative `src/cc-cream.js`, and Claude Code hit `MODULE_NOT_FOUND` (exit 1) on every render — and `/cc-cream:uninstall` was gone, so the only fix was hand-editing `settings.json`. The auto-update command now captures the resolved version dir in `$d` and short-circuits with `[ -z "$d" ] && exit 0`, so an orphaned status line is inert (silent, exit 0) instead of a recurring error. "Degrade, never crash." New installs/auto-wires get the guarded command; existing users pick it up on their next `/cc-cream:setup`.
+
 ## [0.1.14] — 2026-05-29
 
 ### Changed
@@ -124,6 +134,8 @@ line and prints a colored ≤3-row bar — zero tokens, the model never sees it.
 - Supports **macOS and Linux**; Windows is a planned fast-follow.
 - Requires Claude Code **2.1.132+** (`effort` / `thinking` need 2.1.145+).
 
+[0.1.16]: https://github.com/bart-turczynski/cc-cream/compare/v0.1.15...v0.1.16
+[0.1.15]: https://github.com/bart-turczynski/cc-cream/compare/v0.1.14...v0.1.15
 [0.1.6]: https://github.com/bart-turczynski/cc-cream/compare/v0.1.5...v0.1.6
 [0.1.5]: https://github.com/bart-turczynski/cc-cream/compare/v0.1.4...v0.1.5
 [0.1.4]: https://github.com/bart-turczynski/cc-cream/compare/v0.1.3...v0.1.4

package/README.md

@@ -118,13 +118,24 @@ and you may need to **restart** it for the bar to appear.
 
 ### Uninstall
 
-Plugin users — two steps (Claude Code can't clean `settings.json` when a plugin
-is removed, so the wiring is cleared separately from the cache):
+Plugin users — two steps, **in this order** (Claude Code can't clean
+`settings.json` when a plugin is removed, so the wiring is cleared separately
+from the cache):
 ```
-/cc-cream:uninstall          # removes the statusLine wiring
-/plugin uninstall cc-cream   # drops the plugin from the cache
+/cc-cream:uninstall          # 1. removes the statusLine wiring (run this FIRST)
+/plugin uninstall cc-cream   # 2. drops the plugin from the cache
 ```
 
+> **Order matters.** `/cc-cream:uninstall` lives inside the plugin, so once you
+> run `/plugin uninstall` it's gone. The status line itself degrades to nothing
+> if the cache is missing (it won't error), but the now-inert `statusLine` block
+> lingers in `settings.json`. To clear it after the plugin is already gone, run
+> the npm bin (no global install needed):
+> ```bash
+> npx -y -p cc-cream cc-cream-setup --uninstall
+> ```
+> or remove the `statusLine` key from `~/.claude/settings.json` by hand.
+
 npm / manual users:
 ```bash
 cc-cream-setup --uninstall                 # npm (add --purge to also remove runtime + config)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cc-cream",
-  "version": "0.1.14",
+  "version": "0.1.16",
   "description": "Claude Code cache/context/cost status-line tool",
   "directories": {
     "doc": "docs"

package/src/cc-cream.js

@@ -3,10 +3,11 @@
 // Reads the session JSON Claude Code pipes on stdin and prints a colored
 // <=3-row bar. Hard rule: degrade, never crash.
 
+import { realpathSync } from 'node:fs';
 import os from 'node:os';
 import path from 'node:path';
 import process from 'node:process';
-import { pathToFileURL } from 'node:url';
+import { fileURLToPath, pathToFileURL } from 'node:url';
 import { loadConfig, readConfigFile } from './config.js';
 import { render } from './render.js';
 import {
@@ -72,6 +73,23 @@ async function main() {
   process.exit(0);
 }
 
-if (import.meta.url === pathToFileURL(process.argv[1] || '').href) {
+// Robust "is this module the entrypoint?" check. Node's ESM loader canonicalizes
+// import.meta.url (symlinks resolved), but process.argv[1] stays as it was invoked.
+// A plain href comparison therefore fails silently when cc-cream runs from a
+// symlinked path — e.g. a ~/.claude managed by a dotfile manager (stow/chezmoi/yadm)
+// or synced via iCloud/Dropbox — skipping main() so the bar renders NOTHING with no
+// error. Comparing realpaths makes the symlinked and canonical paths match. Falls
+// back to the href comparison if realpath fails (e.g. a path that no longer exists).
+function isEntrypoint() {
+  const arg = process.argv[1];
+  if (!arg) return false;
+  try {
+    return realpathSync(fileURLToPath(import.meta.url)) === realpathSync(arg);
+  } catch {
+    return import.meta.url === pathToFileURL(arg).href;
+  }
+}
+
+if (isEntrypoint()) {
   main();
 }

package/src/install.js

@@ -28,8 +28,16 @@ const TRUST_NOTE =
 // 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.
+//
+// The resolved dir is captured in `$d` and GUARDED with `[ -z "$d" ] && exit 0`:
+// when the glob matches nothing — the state left behind if a user runs
+// `/plugin uninstall cc-cream` WITHOUT first running `/cc-cream:uninstall`, so a
+// stale statusLine outlives the deleted cache — the command degrades to a silent
+// exit 0 instead of running a bare relative `src/cc-cream.js` that crashes with
+// MODULE_NOT_FOUND on every render. "Degrade, never crash" (CLAUDE.md). `exec`
+// replaces the shell so stdin/stdout pass straight through to the renderer.
 export function autoUpdateCommand(nodePath) {
-  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"`;
+  return `d="$(ls -1d "\${CLAUDE_CONFIG_DIR:-$HOME/.claude}"/plugins/cache/*/cc-cream/*/ 2>/dev/null | grep -E '/[0-9]+(\\.[0-9]+)+/$' | sort -V | tail -1)"; [ -z "$d" ] && exit 0; exec ${nodePath} "\${d}src/cc-cream.js"`;
 }
 
 // `desired` is considered already installed if it matches the planned command