npm - ccgauge - Versions diffs - 1.2.0 → 1.2.3 - Mend

ccgauge 1.2.0 → 1.2.3

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.

Files changed (45) hide show

package/CHANGELOG.md CHANGED Viewed

@@ -5,6 +5,78 @@ All notable changes to **ccgauge** are documented here.
 The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and
 this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+## [1.2.3] — 2026-07-08
+Two fixes to the `/usage` overview area.
+### Fixed
+- **The "Overview" toggle now actually hides the overview.** The eye button in
+  the Usage header is meant to collapse the KPI cards *and* the trend chart in
+  one click (its own tooltip reads "KPIs + trend"), leaving just the Requests
+  table. But neither element carried the `.usage-overview-block` class the CSS
+  targets, so the button flipped its state and nothing moved. The KPI grid, the
+  Trend section, and both of their loading skeletons now carry the class, so the
+  toggle collapses and restores the whole overview as intended.
+- **Restored the gap between the trend chart and the Requests table.** The
+  Requests section was missing its top margin and sat flush against the trend
+  card; it now uses `mt-4` to match the vertical rhythm of the rest of the page.
+## [1.2.2] — 2026-06-19
+Fixes a real footgun in the v1.2.0 Codex fast-tier multiplier: the result of
+reading `~/.codex/config.toml` was memoized at module load, so toggling
+`service_tier` required a full server restart to take effect. The detection
+logic itself is intentionally kept identical to ccusage's
+`adapter/codex/speed.rs` — that's the only practical proxy available, since
+the rollout JSONL doesn't record the active service tier per turn.
+### Fixed
+- **No more boot-time cache on the fast-tier detection.**
+  `detectCodexFastTier()` now re-reads `config.toml` on every call (a
+  ~few-hundred-byte read per request, negligible). Live verification: with
+  `service_tier="fast"` Codex totals come in at \$256.76; flip to
+  `"default"` mid-session and the next `/api/turns` request reports \$102.70
+  with `codexFastActive=false`; flip back to `"fast"` and it returns to
+  \$256.76 — all without touching the process.
+### Known limitation
+- **Per-turn fast-mode is unrecoverable from rollout data.** If you toggle
+  `service_tier` over time, historical turns recorded under the previous
+  setting are still billed at the *current* setting's rate. ccusage
+  v20.0.14 has the same behavior. The dashboard reflects "what would my
+  bill be if every Codex turn ran under the active tier", not absolute
+  historical truth — there is no field in the rollout JSONL that records
+  the tier at API-call time (verified by exhaustive inspection of every
+  payload across `token_count` / `session_meta` / `turn_context` events
+  plus `~/.codex/.codex-global-state.json`).
+## [1.2.1] — 2026-06-18
+Fixes two stacking / clipping bugs on the usage page that made dropdowns
+appear behind or get cut off by surrounding content.
+### Fixed
+- **Filter dropdowns on /usage were painted under the KPI cards.** The
+  custom-range picker (and by extension the model / project filter dropdowns)
+  showed the calendar / option list dimly behind the body content instead
+  of on top. Root cause: `.dash-stagger > *` applies a transform animation,
+  which makes each direct child its own stacking context — the top bar and
+  the body end up as siblings with implicit z-auto, so DOM order wins and
+  the body covers the top bar's popovers. Lifted the PageShell top bar to
+  `relative z-20` so its popovers always win. Same fix benefits every
+  PageShell-based page (sessions / projects / models / settings / overview).
+- **Usage table "Columns" dropdown got clipped by its Section card** when
+  the table filtered down to ~0–2 rows: the card collapsed to ~200 px while
+  the dropdown is ~328 px tall, so the bottom row of column toggles became
+  unreachable. The panel is now portaled to `<body>` (mirroring HoverCard)
+  and pinned to the trigger's bounding rect via `useLayoutEffect`, with
+  scroll / resize listeners keeping it anchored. Click-outside detection
+  now checks both the trigger and the portaled panel.
 ## [1.2.0] — 2026-06-17
 Two big themes: **Codex billing accuracy** is back in line with