cc-cream 0.1.16 → 0.1.17

package/CHANGELOG.md

@@ -4,6 +4,14 @@ 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.17] — 2026-05-29
+
+### Fixed
+- **`cc-cream-setup` and the `/cc-cream:*` slash commands silently did nothing when `~/.claude` is a symlink.** `install.js` had the same symlink-fragile entrypoint guard fixed in the renderer for 0.1.16 (`import.meta.url` is canonicalized by Node's ESM loader; `process.argv[1]` is not), so running it from a symlinked path skipped `main()` entirely — exit 0, no output, settings.json untouched. The "am-I-the-entrypoint?" check is now a single symlink-robust helper (`isEntrypoint` in `src/utils.js`) shared by both `cc-cream.js` and `install.js`. Caught by the new install-journey smoke tests.
+
+### Added
+- **End-to-end install/uninstall journey smoke tests** (`features/27-install-journey.feature`, CREAM-fxsusmgd). They stage a real plugin cache the way `/plugin install` lays it out, run the actual `SessionStart` hook and `install.js` as child processes, and execute the baked statusLine command through `sh -c` exactly as Claude Code does — guarding the *seams* unit specs can't: cache layout, the settings.json lifecycle, command order, the empty-cache guard (0.1.15), and symlinked config dirs (0.1.16). CI-safe; no live `claude` CLI needed.
+
 ## [0.1.16] — 2026-05-29
 
 ### Fixed
@@ -134,6 +142,7 @@ 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.17]: https://github.com/bart-turczynski/cc-cream/compare/v0.1.16...v0.1.17
 [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

package/package.json

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

package/src/cc-cream.js

@@ -3,11 +3,9 @@
 // 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 { fileURLToPath, pathToFileURL } from 'node:url';
 import { loadConfig, readConfigFile } from './config.js';
 import { render } from './render.js';
 import {
@@ -17,6 +15,7 @@ import {
   readState,
   writeState,
 } from './state.js';
+import { isEntrypoint } from './utils.js';
 
 export { DEFAULTS } from './defaults.js';
 export { loadConfig } from './config.js';
@@ -73,23 +72,9 @@ async function main() {
   process.exit(0);
 }
 
-// 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()) {
+// isEntrypoint (src/utils.js) is symlink-robust — see its comment. A plain
+// import.meta.url === pathToFileURL(argv[1]) check fails under a symlinked path and
+// renders nothing with no error.
+if (isEntrypoint(import.meta.url)) {
   main();
 }

package/src/install.js

@@ -14,7 +14,7 @@ import os from 'node:os';
 import path from 'node:path';
 import process from 'node:process';
 import readline from 'node:readline';
-import { pathToFileURL } from 'node:url';
+import { isEntrypoint } from './utils.js';
 
 const TRUST_NOTE =
   'Claude Code must be trusted and possibly restarted for the status line to appear.';
@@ -328,6 +328,9 @@ async function main() {
   }
 }
 
-if (import.meta.url === pathToFileURL(process.argv[1] || '').href) {
+// isEntrypoint (src/utils.js) is symlink-robust: a plain href comparison fails when
+// install.js runs from a symlinked path (e.g. a dotfile-managed ~/.claude), which
+// would make `cc-cream-setup` / the slash commands silently do nothing.
+if (isEntrypoint(import.meta.url)) {
   main();
 }

package/src/utils.js

@@ -1,5 +1,25 @@
+import { realpathSync } from 'node:fs';
+import process from 'node:process';
+import { fileURLToPath, pathToFileURL } from 'node:url';
 import { ANSI } from './defaults.js';
 
+// Robust "is this module the process entrypoint?" check, shared by every module
+// that may run both as a script and as an import (cc-cream.js, install.js). Node's
+// ESM loader canonicalizes import.meta.url (symlinks resolved) but leaves
+// process.argv[1] as-invoked, so a plain href comparison fails when the module runs
+// from a symlinked path — e.g. a ~/.claude managed by a dotfile manager
+// (stow/chezmoi/yadm) or synced via iCloud/Dropbox — silently skipping main().
+// Comparing realpaths fixes it; falls back to the href compare if realpath throws
+// (e.g. a path that no longer exists). Pass the caller's import.meta.url.
+export function isEntrypoint(metaUrl, arg = process.argv[1]) {
+  if (!arg) return false;
+  try {
+    return realpathSync(fileURLToPath(metaUrl)) === realpathSync(arg);
+  } catch {
+    return metaUrl === pathToFileURL(arg).href;
+  }
+}
+
 export const clone = (o) => JSON.parse(JSON.stringify(o));
 export const isNum = (v) => typeof v === 'number' && Number.isFinite(v);
 export const numOr = (v, d) => (isNum(v) ? v : d);