@promptctl/cc-candybar 1.158.0 → 1.159.0

package/README.md

@@ -122,6 +122,8 @@ These are the segment names `DEFAULT_DSL_CONFIG` declares, each available to a u
 | `metrics` | `Δ` last response time, `⧖` response time, `⧗` session duration, `◆` message count, lines changed | when any of those exist |
 | `activity` | `⌘` the slash command that opened the turn, `☐` the in-progress todo with its position, `⟳` tools in flight and `✓` tools finished this turn | while the session is doing something |
 
+Every bar also carries, right after the settings menu's door, a cell saying how it is redrawn: `30 fps` while an animation lane draws it and it moves where you can see it, ` 1 fps` while that lane's bar is still or off screen, and `polled` when Claude Code reruns the statusline itself. It sits wherever the door does, so no layout has to place it, and none can leave it out.
+
 The lit ticket a checkout is working on is not bundled: it is a plugin, installed with `cc-candybar plugin install promptctl/links-issue-tracker`, whose one segment (`plugins.lit.ticket`, each of its parts a setting) is in edit mode's add-segment library. It reads the `.lit/statusline.json` lit keeps in each checkout, so no lit process runs for the bar.
 
 Each segment is a DSL declaration with a `template` (text + interpolation + style functions), a `bg`/`fg` palette spec, and optional `when` predicate. Templates compose freely — every formatter in the bundled function library (`formatCost`, `formatTokens`, `formatLongTimeRemaining`, `budgetStatus`, `link`, `urlEncode`, the sprig string/list/dict library, …) is available in every segment.