cc-cream 0.1.7 → 0.1.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -4,6 +4,15 @@ All notable changes to cc-cream are documented here. Format follows
4
4
  [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); versions follow
5
5
  [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
6
6
 
7
+ ## [0.1.8] — 2026-05-29
8
+
9
+ ### Added
10
+ - **`cc-cream-setup` bin for npm users** (CREAM-gvrvnhsc). `npm install -g cc-cream` now exposes a first-class `cc-cream-setup` command (and `cc-cream-setup --uninstall` / `--purge`) that runs the consent installer, replacing the clunky `node $(npm root -g)/cc-cream/src/install.js`. The existing `cc-cream` bin remains the status-line renderer.
11
+ - **CI workflow that runs the publish gate on a CLI-less runner** (CREAM-xzhidmjt). `.github/workflows/ci.yml` runs `npm test` — the exact command `prepublishOnly` runs — on every PR and push to `main`, and asserts the `claude` CLI is absent so it mirrors the npm-publish environment.
12
+
13
+ ### Changed
14
+ - **Publish gate is now CI-safe by construction** (CREAM-xzhidmjt). Scenarios that shell out to a live `claude` are tagged `@needs-cli` and excluded from the default cucumber profile (`not @manual and not @needs-cli`); run them with `npm run test:cli`. Previously such a scenario could go `pending` on a runner without the CLI and silently break `npm publish` — now any regression of that kind fails on the PR instead.
15
+
7
16
  ## [0.1.7] — 2026-05-29
8
17
 
9
18
  ### Fixed
package/README.md CHANGED
@@ -76,20 +76,21 @@ The `/cc-cream:setup` command runs the consent installer, which writes the
76
76
  `/plugin update` drops a new version into the cache, the next render picks it
77
77
  up without any further action.
78
78
 
79
- ### Option 2 — npm / npx
79
+ ### Option 2 — npm
80
80
 
81
81
  ```bash
82
- npx -y cc-cream@latest
82
+ npm install -g cc-cream
83
83
  ```
84
84
 
85
- Or install globally:
85
+ Then wire it into Claude Code with the bundled CLI:
86
86
  ```bash
87
- npm install -g cc-cream
87
+ cc-cream-setup
88
88
  ```
89
89
 
90
- Then run the consent installer to wire it into Claude Code:
90
+ `cc-cream-setup` runs the consent installer (`src/install.js`). Without a global
91
+ install you can run it through npx:
91
92
  ```bash
92
- node $(npm root -g)/cc-cream/src/install.js
93
+ npx -y -p cc-cream cc-cream-setup
93
94
  ```
94
95
 
95
96
  ### Option 3 — Manual GitHub clone
@@ -119,8 +120,8 @@ Plugin users:
119
120
 
120
121
  npm / manual users:
121
122
  ```bash
122
- node $(npm root -g)/cc-cream/src/install.js --uninstall # npm
123
- node cc-cream/src/install.js --uninstall # manual clone
123
+ cc-cream-setup --uninstall # npm (add --purge to also remove config)
124
+ node cc-cream/src/install.js --uninstall # manual clone
124
125
  ```
125
126
 
126
127
  Uninstall removes the `statusLine` block **only if it is cc-cream's** — a
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "cc-cream",
3
- "version": "0.1.7",
3
+ "version": "0.1.8",
4
4
  "description": "Claude Code cache/context/cost status-line tool",
5
5
  "directories": {
6
6
  "doc": "docs"
@@ -12,6 +12,7 @@
12
12
  "pretest": "npm run lint && npm run knip && npm run validate",
13
13
  "test": "cucumber-js",
14
14
  "test:manual": "cucumber-js --profile manual",
15
+ "test:cli": "cucumber-js --profile cli",
15
16
  "coverage": "c8 cucumber-js",
16
17
  "watch": "cucumber-js --watch",
17
18
  "hooks": "simple-git-hooks",
@@ -21,7 +22,8 @@
21
22
  "pre-push": "npm run coverage"
22
23
  },
23
24
  "bin": {
24
- "cc-cream": "src/cc-cream.js"
25
+ "cc-cream": "src/cc-cream.js",
26
+ "cc-cream-setup": "src/install.js"
25
27
  },
26
28
  "files": [
27
29
  "src/",