feat(widgets): add editable label prefix to text-label widgets - #601

…es (#10)

* feat(widgets): compact label presets with global and per-widget toggles

Add abbreviated label presets for labeled widgets, complementary to the
free-form label editing proposed upstream (sirmalloc#601):

- New `compactLabels` settings flag (default off). Additive v4 key: old
  configs parse unchanged and render identically, no version bump needed.
- Presets live in one map (`Model:` -> `M:`, `Context:` -> `Ctx:`,
  `Cost:` -> `` — the value's own `$` is the glyph) inside
  `formatRawOrLabeledValue`, so every widget routed through the helper
  picks them up with no per-widget changes. Model, Session Cost, and
  Context Bar moved onto the helper.
- One-click global toggle in Global Overrides `(j)`; per-widget override
  via `(j) compact label` in the items editor (metadata `compactLabel`),
  which wins over the global setting in both directions. Capability for
  the editor keybind is derived from a cached preview probe of the
  widget registry.
- Extend the Git Branch width-cap pattern to Current Working Dir and
  Session Name (`w` max-width keybind).
- Document per-widget padding/separator/label width overhead in
  docs/USAGE.md; defaults unchanged.

Tests: preset resolution, toggle metadata, global injection precedence,
migration parity (v1->v4 and schema-less v4 parse), registry-wide `j`
keybind reservation, capable-type probe sanity, Global Overrides `(j)`
keystroke test. bun test 2400 pass; bun run lint clean.

Co-Authored-By: Claude Code <[email protected]>

* fix(tui): compact-label toggle cycles over the effective state

The per-widget (j) toggle only wrote/removed 'true', so with the global
Compact Labels setting on it became a visual no-op: the render-time
injection re-compactified the widget after the key was removed, and no
row marker showed the effective state.

- toggleCompactLabel now takes the settings and cycles the EFFECTIVE
  state: compact (saved 'true' or inherited global on) -> write 'false';
  forced off -> drop the key and inherit; otherwise -> write 'true'.
- getCompactLabelModifierText reports the effective state:
  '(compact label)' / '(compact label: on)' / '(compact label: off)'.
- ItemsEditor/input-handlers pass settings through to both.
- docs/USAGE.md: fix preset savings arithmetic (Model -4, Context -4).

Co-Authored-By: Claude Code <[email protected]>

* test(renderer): cover (j) toggle forcing labels off while global compact is on

Co-Authored-By: Claude Code <[email protected]>

* style: fix import order in compact-labels renderer test

Co-Authored-By: Claude Code <[email protected]>

---------

Co-authored-by: axisrow <[email protected]>
Co-authored-by: Claude Code <[email protected]>

sirmalloc#601 lets Tokens Input, Output, Cached and Total, and Git Staged,
Unstaged and Untracked Files, offer their labels to the label editor
one widget at a time. #16 and #22 move those widgets onto shared base
classes, so the merges kept their shape and the labels went with it:
an edited label still drew, but the editor never offered (e).

Each base now offers its subclass's label, once for all of them.

Upstream's label editor (sirmalloc#601) gives each widget one default label,
while Extra Usage Used, Remaining and Utilization pick "Overage" or
"Spend" by account. The editor offers the Overage label, since it has
no usage data, and an edited label replaces whichever one the account
would show.

Upstream's label editor (sirmalloc#601) gives each widget one default label,
while Extra Usage Used, Remaining and Utilization pick "Overage" or
"Spend" by account. The editor offers the Overage label, since it has
no usage data, and an edited label replaces whichever one the account
would show.

Upstream's label editor (sirmalloc#601) drops a widget's label when its type
changes, since the label names the old widget's value ("Model: " on
Session Cost). It does that where the picker applies a type change,
which this branch moves into placePickerSelection so the live preview
and Enter share it. The label drop moves there too, so the preview
shows the line without the old label, as Enter applies it.

…lors

Upstream's label editor (sirmalloc#601) lets Thinking Effort's "Thinking: " be
edited, but this branch draws the widget through formatThinkingEffort,
which wrote the label itself. It now draws the edited label, or none,
inside the brackets and in the widget color, and the default comes from
one constant that getLabelPrefix shares.

This branch also merges the label-key branch (#48): its (b)rackets key
would otherwise clash with upstream's la(b)el… on a labeled widget.

…ication

Brings in upstream main, including the label editor (sirmalloc#601). Where sirmalloc#601
meets this branch's shared bar code:
- The bar widgets draw a bar through formatUsageBar, labeled with the
  widget's getLabelPrefix(item), so a bar mode keeps sirmalloc#601's bar label
  ("Block ", "Reset ") and an edited label.
- Context % and Context % (usable) declare their label once, on
  ContextPercentageWidgetBase; the usage widgets on UsagePercentWidget.

Brings in upstream main, including the label editor (sirmalloc#601). This branch
draws Model through formatModelName, which wrote "Model: " itself, so
it now draws the edited label, or none, in the widget color; the
default comes from one constant that getLabelPrefix shares.

…t/value-coloring

Brings in Extra Usage Today with upstream main merged. Value colors draw
their widget's label themselves, so with upstream's label editor (sirmalloc#601)
formatColoredValue now draws the edited label, or none, in the widget
color.

Extra Usage Today, Daily Budget, Extra Usage Limit, Session Cost Rate
and Daily Cost Rate declare their default labels, so (e)dit label offers
them as upstream's label editor (sirmalloc#601) does for its own widgets. The
editor's default for Extra Usage Today and Limit is the "Overage"
label, since it has no usage data; accounts without plan limits show
"Spend". Each builds that label in one place for the editor and render.

So "today: $12.34 of $50.00/day" is Extra Usage Today labeled "today: ",
Daily Budget labeled "of " and a "/day" Custom Text, with no raw values.

With the label editor (sirmalloc#601) in main, anyone on a usage-based Enterprise
plan can relabel the Extra Usage widgets' "Overage" to "Spend" in a few
keys, so detecting those accounts from the usage API's response shape
isn't worth its cache field and heuristics.

What stays is the wording: the three widgets' descriptions say they
cover Pro/Max overage and Enterprise spend, the docs say the same and
point at the label editor, and picker searches for "enterprise" or
"spend" list the three widgets first, which a new test checks.

Conflict resolutions:
- Label override (upstream sirmalloc#601): fork widgets keep their own rendering and
  read the label through getLabelPrefix/getLabel, so per-item label overrides
  apply. Raw mode keeps the fork's metadata.prefix.
- Usage percent widgets (upstream sirmalloc#545 moved them onto a shared module): the
  fork's SessionUsage, WeeklyUsage, WeeklyOpusUsage and WeeklySonnetUsage keep
  their own implementations (pace indicator, monthly/weekly promotion, cursor),
  so they do not take label overrides. FableWeeklyUsage, unchanged in the fork,
  uses the upstream shared module.
- BlockResetTimer keeps the "Weekly Reset" label when weekly is promoted into
  the session slot, now derived from the mode-aware upstream label.
- ContextLength keeps the fork's resolveContextLengthTokens fallback instead of
  the upstream tokenMetrics branch.
- MonthlyUsage now honors the configured percent number format, which the
  shared upstream usage widget test suite checks.

…s too (#670)

* feat: label Extra Usage as spend on accounts without plan limits

On usage-based plans (Claude Enterprise) the usage API reports every
rate-limit window as null and no limits[] entries: there's no plan limit
to go over, and extra usage is the account's whole spend. The Extra
Usage widgets still called it overage ("Overage Used: $123.45"), and
their picker descriptions only mentioned pay-as-you-go overage, so
Enterprise users had no reason to think these widgets were theirs.
Searching the picker for "enterprise" or "spend" didn't find them.

The parser now flags a response that explicitly reports no plan limits
(`noPlanLimits`). The flag is kept in the usage cache and through the
merge with statusline rate_limits, and the three widgets label their
value "Spend Used", "Spend Left" and "Spend" when it's set. Only an
explicit null counts and any limits[] entry counts as a limit, so every
uncertain case keeps the "Overage" label. A cache written before this
change keeps the old label until its next refresh.

The widget descriptions now mention both Pro/Max overage and Enterprise
spend, which also makes the picker's search find them.

* test: cover the Spend label with an edited label

Upstream's label editor (#601) gives each widget one default label,
while Extra Usage Used, Remaining and Utilization pick "Overage" or
"Spend" by account. The editor offers the Overage label, since it has
no usage data, and an edited label replaces whichever one the account
would show.

* refactor: keep the Enterprise wording, drop the Spend label detection

With the label editor (#601) in main, anyone on a usage-based Enterprise
plan can relabel the Extra Usage widgets' "Overage" to "Spend" in a few
keys, so detecting those accounts from the usage API's response shape
isn't worth its cache field and heuristics.

What stays is the wording: the three widgets' descriptions say they
cover Pro/Max overage and Enterprise spend, the docs say the same and
point at the label editor, and picker searches for "enterprise" or
"spend" list the three widgets first, which a new test checks.

* test: check the picker lists the Extra Usage widgets first, however many there are

* test: look for the Extra Usage widgets among the widgets that mention the word

* refactor(widgets): share Extra Usage Used and Remaining's code

The two widgets were the same class apart from how the amount is worked
out, and their label, name, description and preview sample. They now
extend ExtraUsageAmountWidget, the way the Tokens widgets share
TokenCountWidget. Rendering is unchanged.