cc-cream 0.3.2 → 0.3.3

package/CHANGELOG.md

@@ -6,6 +6,15 @@ All notable changes to cc-cream are documented here. Format follows
 
 ## [Unreleased]
 
+## [0.3.3] — 2026-05-30
+
+### Changed
+- **The post-publish `npx` smoke test now uses `--safe-chain-skip-minimum-package-age`** so the `@manual` "npm indexing" scenario works immediately after a release without waiting for the package-age guard to lift (CREAM-elrbkfot).
+- **TTL segment now displays minutes only** (`ttl:60`, `ttl:8`, `ttl:0`) instead of the previous `HH:MM` format (`ttl:01:00`). Simpler to read at a glance; matches the 60-second refresh cadence (CREAM-vhhdhydn).
+
+### Documentation
+- **The `cache` segment's `drop` / `drop_recover` config keys are now documented.** They've been live since cache drop-detection shipped but never appeared in the README — the segment catalog listed `cache` as "neutral" with no mention that it turns red on a sharp hit-rate drop, nor that the trip/recover thresholds are configurable. Added a "`cache` drop detection" subsection, surfaced the keys in the example config, and corrected the catalog color note. This is the documentation outcome of CREAM-wwsdavum (configure-via-`/cc-cream:` command), which is otherwise declined as a dup of the deliberately-closed CREAM-udibxkch.
+
 ## [0.3.2] — 2026-05-30
 
 ### Fixed

package/README.md

@@ -160,8 +160,8 @@ message — restart an already-open session to drop it immediately.
 > # add --purge to also remove your config
 > ```
 > The npm bin does the same job, but **not always**: a *freshly published* version
-> is blocked by npm's min-package-age safe-chain guard (it reports "command not
-> found") until it ages in, so use it only if the cache route isn't handy:
+> is blocked by npm's min-package-age safe-chain guard (it reports "No versions
+> available") until it ages in, so use it only if the cache route isn't handy:
 > ```bash
 > npx -y -p cc-cream cc-cream-setup --uninstall
 > ```
@@ -210,7 +210,7 @@ cc-cream-setup --check-config   # reports unknown keys / out-of-domain values; e
   "percentage": "consumed",
   "segments": {
     "ctx":          { "on": true,  "row": 1, "order": 2, "amber": 30, "orange": 40, "red": 50, "basis": "window", "ceiling": 200000, "display": "basis" },
-    "cache":        { "on": true,  "row": 1, "order": 3 },
+    "cache":        { "on": true,  "row": 1, "order": 3, "drop": 20, "drop_recover": 80 },
     "write":        { "on": false, "row": 1, "order": 3.5 },
     "ttl":          { "on": true,  "row": 1, "order": 4, "amber": 50, "red": 80 },
     "cost":         { "on": true,  "row": 1, "order": 5 },
@@ -254,7 +254,7 @@ Colored segments additionally accept threshold keys. Thresholds mark the
 | Segment | Default | Example | Meaning | Color |
 |---|---|---|---|---|
 | `ctx` | on, row 1 | `ctx:19% [38k]` | context-window occupancy + input-token magnitude | `<30` green · `30–40` amber · `40–50` orange · `≥50` red |
-| `cache` | on, row 1 | `cache:95%` | last-turn cache hit rate (reads / total tokens) | neutral |
+| `cache` | on, row 1 | `cache:95%` | last-turn cache hit rate (reads / total tokens) | neutral; **red** on a sharp drop (see below) |
 | `write` | **off**, row 1 | `write:4%` | last-turn cache creation rate (new writes / total tokens) | neutral |
 | `ttl` | on, row 1 | `ttl:00:52` | time remaining before cache expires (counts down to 00:00) | `<50%` green · `50–80%` amber · `≥80%` red |
 | `cost` | on, row 1 | `~$4.50` | session cost incl. subagents; `~` = CC's estimate | neutral; hidden when zero |
@@ -301,6 +301,18 @@ default row via config must land in a zone to appear on row 1.
 
 Default: `amber: 30`, `orange: 40`, `red: 50` (percent consumed).
 
+### `cache` drop detection
+
+The `cache` segment stays neutral while the hit rate is healthy, but turns **red**
+when it falls sharply from one turn to the next — a cue that the prompt cache was
+just invalidated (e.g. an edit far back in context forced a re-read). This relies
+on per-session state, so it only fires when `session_id` is present in stdin.
+
+- `drop`: percentage-point fall from the previous turn that trips red. Default `20`
+  (95% → 74% trips; 95% → 80% does not).
+- `drop_recover`: once tripped, the segment stays red until the hit rate climbs
+  back to at least this value. Default `80`.
+
 ### `ttl` thresholds
 
 Default: `amber: 50`, `red: 80` (percent of the resolved TTL consumed).

package/package.json

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

package/src/segments.js

@@ -63,7 +63,7 @@ function segTtl(cfg, ttlMin, now, anchorMs) {
   if (!isNum(anchorMs)) return null;
   const elapsedMin = Math.floor(Math.max(0, now - anchorMs) / 60000);
   const remainingMin = Math.max(0, ttlMin - elapsedMin);
-  const text = `ttl:${pad2(Math.floor(remainingMin / 60))}:${pad2(remainingMin % 60)}`;
+  const text = `ttl:${remainingMin}`;
   const s = cfg.segments.ttl;
   const pctTtl = ttlMin > 0 ? (elapsedMin / ttlMin) * 100 : 0;
   return { text, color: band(pctTtl, s.amber, s.red) };