cc-cream 0.1.12 → 0.1.14

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.14] — 2026-05-29
+
+### Changed
+- **The status bar now turns itself on — no manual `/cc-cream:setup` for fresh installs** (CREAM-nywsljfq). Claude Code can't let a plugin contribute the main status line natively (only `agent`/`subagentStatusLine` are plugin-settable — verified by probe), so the bar still needs a write to `settings.json`. Instead of making you run `/cc-cream:setup`, the `SessionStart` hook (`hooks/auto-setup.js`, renamed from `setup-reminder.js`) now **auto-wires** cc-cream's `statusLine` on the first session after install — but **only when no status line is configured**. It never clobbers a status line you set for something else (that still routes through the interactive `/cc-cream:setup`), and a one-shot marker means it never re-adds the bar after you remove it with `/cc-cream:uninstall`. The nudge to run `/cc-cream:setup` now appears only in the foreign-status-line case. Output stays a single `systemMessage` (zero model tokens). You may need to restart/trust the workspace for the bar to appear.
+
+## [0.1.13] — 2026-05-29
+
+### Fixed
+- **Setup/uninstall commands showed no visible feedback** (regression from 0.1.12). Trimming the command `.md` bodies to just the bang line removed the only part Claude Code surfaces prominently — a slash command's bang (`` !`…` ``) output is folded into the model prompt, not shown to the user — so running `/cc-cream:setup` appeared to do nothing. Restored a brief one-line note to each command body (visible confirmation of what's happening), while keeping the expensive statusLine-JSON echo out of `install.js` (the real token win from 0.1.12). Net: still far cheaper than ≤0.1.11, but the command no longer looks silent.
+
 ## [0.1.12] — 2026-05-29
 
 ### Changed

package/README.md

@@ -66,16 +66,21 @@ To use the self-hosted marketplace directly:
 /plugin install cc-cream
 ```
 
-Then wire it into your settings in one step:
+That's usually all you need: on the first session after install, cc-cream
+**auto-wires** its `statusLine` into `~/.claude/settings.json` (you may need to
+restart or trust the workspace for the bar to appear). It only does this when no
+status line is configured — it never overwrites one you set for something else,
+and it never re-adds the bar after you remove it.
+
+If you already have a status line and want to replace it with cc-cream's, run:
 ```
 /cc-cream:setup
 ```
 
 The `/cc-cream:setup` command runs the consent installer, which writes the
-`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.
+`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.
 
 ### Option 2 — npm
 

package/package.json

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

package/src/install.js

@@ -49,7 +49,7 @@ function isInstalled(existing, command) {
 // (dev repo, copied home runtime, or the plugin cache-glob) — every command
 // references the cc-cream entrypoint. Used by uninstall so we never touch a
 // statusLine the user wired for something else.
-function isCcCreamStatusLine(existing) {
+export function isCcCreamStatusLine(existing) {
   return (
     !!existing &&
     typeof existing === 'object' &&
@@ -187,7 +187,7 @@ function copyRuntimeFiles(sourceFile, destDir) {
 // PATH, so a bare `node` is unsafe. We prefer the shell's `command -v node`
 // (the path the user's interactive shell would pick), falling back to
 // process.execPath (the node currently running setup) if that fails.
-function resolveNodePath() {
+export function resolveNodePath() {
   try {
     const found = execSync('command -v node', { encoding: 'utf8' }).trim();
     if (found) return found;