pi-minimal-footer 0.8.0 → 0.9.0

package/CHANGELOG.md

@@ -7,6 +7,26 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.9.0] - 2026-10-30
+
+### Added
+
+- Optional provider prefix (`minFooter.showProvider`) and colored thinking level (`minFooter.showThinking`), both off by default. Thanks to [@mkaros2025].
+- Hide subscription usage and stop its background queries with `minFooter.showUsage: false`. Thanks to [@mkaros2025].
+- Other extensions can show or hide subscription usage for the session without changing saved preferences (`pi-minimal-footer:set-usage-enabled`).
+
+### Changed
+
+- Context label turns yellow at 85% and red at 92% of the configured compaction threshold.
+
+## [0.8.1] - 2026-10-28
+
+### Fixed
+
+- Apply changed context-display settings immediately when enabling the footer or starting a session
+- Prevent outdated Git counts and highlights after switching directories, replacing the footer, or disabling it
+- Correct documentation and previews to match current context formatting, usage-bar behavior, and settings
+
 ## [0.8.0] - 2026-10-28
 
 ### Added
@@ -273,7 +293,11 @@ First npm-ready release.
 
 - Project scaffold — `extensions/index.ts` with basic footer structure, `package.json` with pi extension manifest, `README.md`, `LICENSE` (MIT)
 
-[Unreleased]: https://github.com/Ryu-CZ/pi-minimal-footer/compare/v0.8.0...HEAD
+[@mkaros2025]: https://github.com/mkaros2025
+
+[Unreleased]: https://github.com/Ryu-CZ/pi-minimal-footer/compare/v0.9.0...HEAD
+[0.9.0]: https://github.com/Ryu-CZ/pi-minimal-footer/compare/v0.8.1...v0.9.0
+[0.8.1]: https://github.com/Ryu-CZ/pi-minimal-footer/compare/v0.8.0...v0.8.1
 [0.8.0]: https://github.com/Ryu-CZ/pi-minimal-footer/compare/v0.7.1...v0.8.0
 [0.7.1]: https://github.com/Ryu-CZ/pi-minimal-footer/compare/v0.7.0...v0.7.1
 [0.7.0]: https://github.com/Ryu-CZ/pi-minimal-footer/compare/v0.6.0...v0.7.0

package/README.md

@@ -9,7 +9,7 @@
 
 An opinionated, compact, one-line status bar for [Pi](https://github.com/earendil-works/pi).
 
-![Footer preview: ~/git/project   main        🧠 Karpathy  🪽 Icarus  model · 42k/200k · [⣿⣿⣿⣤⠀⠀⠀⠀⠀⠀]↻1d8h](media/preview.png)
+![Footer preview: ~/git/project   main ↑2 · 🧠 Karpathy · 🪽 Icarus · gpt-6-sol · 42k/200k · subscription usage with reset time](media/preview.png)
 
 **Left**
 
@@ -31,8 +31,6 @@ Choose one npm name (they contain the same extension; do not install both):
 
 ```bash
 pi install npm:pi-minimal-footer
-# or
-pi install npm:@ryu-cz/pi-minimal-footer
 ```
 
 The scoped package is an official mirror, not a separate extension.
@@ -58,6 +56,9 @@ Edit `minFooter` in Pi's agent `settings.json` (normally `~/.pi/agent/settings.j
     "showPath": true,
     "showModel": true,
     "showContext": true,
+    "showProvider": false,
+    "showThinking": false,
+    "showUsage": true,
     "contextAsPercentage": false,
     "powerlineSeparator": true,
     "gitRefreshSeconds": 91,
@@ -68,7 +69,10 @@ Edit `minFooter` in Pi's agent `settings.json` (normally `~/.pi/agent/settings.j
 }
 ```
 
+- `showProvider` prefixes the model with its provider id, e.g. `opencode-go/deepseek-v4.1-flash`; default `false`.
+- `showThinking` appends the thinking level for reasoning models, e.g. `deepseek-v4.1-flash high` or `thinking off`, in Pi's matching `thinking*` theme color; default `false`.
 - `showSkills` shows **extension status text**, not installed skills. The footer does not add the example statuses itself.
+- `showUsage` enables this footer's own provider usage queries and the subscription usage bar; set it to `false` when another extension already publishes quota; default `true`.
 - Set `powerlineSeparator` to `false` for plain spaces instead of `` / `` if your font lacks those glyphs. The git icon `` and sync arrows also need compatible glyphs; hide Git data with `showGitBranch: false` if needed.
 - `gitRefreshSeconds`: local refresh interval; `1`–`2147483` seconds; default `91`.
 - `gitFetch`: background fetch on startup, then roughly 5 minutes after each attempt completes; failures are silent; default `false`.
@@ -83,7 +87,9 @@ Counts require a configured upstream. Unsynced branches use normal text color; s
 
 ### Context
 
-`42k/200k` means tokens used / context window. Set `"contextAsPercentage": true` under `minFooter` to show `21.0%/200k` instead. Unknown usage shows `?`.
+`42k/200k` means tokens used / context window. Set `"contextAsPercentage": true` under `minFooter` to show `21.0%/200k` instead. Unknown token usage shows `?/200k` when the window is known, or `?` when context information is unavailable.
+
+The whole context label keeps its normal dim color below 85% of Pi’s compaction trigger (`contextWindow - reserveTokens`), turns yellowish (`warning`) at 85%, and red (`error`) at 92%. It uses Pi’s effective compaction settings, including exact `provider/modelId` overrides, with a default reserve of 16,384 tokens. Colors apply in both display modes, even when auto-compaction is disabled. Unknown usage or a non-positive trigger keeps the normal color.
 
 ### Subscription usage
 
@@ -91,7 +97,7 @@ Counts require a configured upstream. Unsynced branches use normal text color; s
 
 - **Bar:** expands into spare space, using 2–10 cells by default, capped by `maxUsageBarCells`. Smaller caps and very narrow terminals may show fewer cells or only the reset label.
 - **Colors:** green below 85%, amber from 85%, red from 92%.
-- **Cached data:** dim after a refresh failure.
+- **Cached data:** dim after a refresh failure or when its reset time has passed.
 - Reset: local `↻HH:mm` through 24 hours; whole days/hours above 24 hours (`↻1d8h`); whole days above 10 days (`↻12d`). Remaining durations round down. No reset reported means bar only.
 - Shows the shortest available usage window for the selected provider. Missing credentials, unsupported/local models, or absent limits hide the usage bar. Custom proxy endpoints are not polled.
 - Virtual/routed models show model and context usage, but no subscription bar.
@@ -119,19 +125,13 @@ Only one footer extension can be active. For plugin integration, see [VISION.md]
 
 ## Programmatic control
 
-Other Pi extensions can enable or disable the footer for the current session without changing saved settings:
+Other Pi extensions can control this footer without changing saved preferences:
 
-```typescript
-pi.events.emit("pi-minimal-footer:set-enabled", { enabled: false }); // disable
-pi.events.emit("pi-minimal-footer:set-enabled", { enabled: true });  // enable
-```
+- **Footer** (`pi-minimal-footer:set-enabled`): enable or disable for the current session.
+- **Subscription usage** (`pi-minimal-footer:set-usage-enabled`): show or hide the bar and its background queries independently—useful when your terminal already shows quota.
+- New sessions and `/reload` restore saved preferences.
 
-- Events work only while this extension's session is active.
-- The latest command or event wins.
-- `/minfooter on/off` saves your preference into config; events don't.
-- Enabling may replace another footer.
-- Disabling restores Pi's default footer if this footer is active; it leaves another extension's active footer untouched.
-- New sessions and `/reload` use your saved preference.
+Event API and integration rules: [developer guide](VISION.md#session-only-footer-control).
 
 ## Development & design
 

package/VISION.md

@@ -9,16 +9,16 @@ The [README](README.md) is the user manual. This document records current design
 ## Layout contract
 
 - Directory and Git branch form the left group, separated by ``.
-- Each extension status is its own `` tab. Preserve the supplied text; do not invent status labels, parentheses, or pipes.
+- Each extension status is its own `` tab. Preserve the supplied text except for replacing line breaks and tabs with spaces; do not invent status labels, parentheses, or pipes.
 - Model, context, and subscription usage form the rightmost group, separated by ` · `. Model identifies the running engine; context describes its usage; the usage bar stays anchored at the right edge.
 - Powerline separators are dim. `powerlineSeparator: false` replaces them with a single space. Font availability cannot be detected reliably.
 - Measure terminal columns with `visibleWidth`, not string length. Preserve ANSI styling and wide-character accounting when truncating.
 
 ### Space allocation
 
-Reserve the usage bar and model/context before allocating location and statuses. Statuses and location may shorten or disappear; on sufficiently narrow terminals, model/context can also shorten or disappear.
+Reserve the usage bar and model/context before allocating location and statuses. Statuses and location may shorten or disappear; on sufficiently narrow terminals, model/context can also shorten or disappear. The model field is one protected unit: an optional `provider/` prefix, the bold model id, and an optional thinking level colored by Pi's `thinking*` theme tokens are truncated together, so the field never splits into separate segments.
 
-Lay out other fields with a two-cell usage bar first. Grow the bar only into leftover columns, up to ten cells—never truncate another field solely to enlarge it. At extreme widths, shrink to one cell, show only the reset label, or hide usage if neither can fit. Brackets keep an empty bar's edges visible and count toward its width, but not its cell cap.
+Lay out other fields with a two-cell usage bar first, or fewer if `maxUsageBarCells` is smaller. Grow the bar only into leftover columns, up to `maxUsageBarCells` (default ten)—never truncate another field solely to enlarge it. At extreme widths, shrink to one cell, show only the reset label, or hide usage if neither can fit. Brackets keep an empty bar's edges visible and count toward its width, but not its cell cap. With `showUsage: false` no bar is reserved at all, and the usage owner is stopped before any credential lookup, request, or timer is created.
 
 Two cells give 6.25% steps; ten give 1.25%. Fill rounds to the nearest eighth-cell step. Only the final partially filled cell uses an intermediate shade:
 
@@ -41,6 +41,7 @@ The bar and reset label have no intervening space. Reset formatting uses local c
 - Default to tokens used / context window, with an explicit `k` suffix on both values. Never deduplicate units across the slash.
 - Always use kilos, including for million-token windows (`1000k`, not `1M`). Below 10k, use two significant digits where one-token resolution permits, capped at three decimal places in kilos: `0.001k`, `0.012k`, `0.11k`, `0.78k`, `0.99k`, `1.0k`, `9.0k`. At and above 10k, round to whole kilos: `10k`, `124k`, `1000k`. Zero is `0k`; rounding can promote `9.999k` to `10k`.
 - `minFooter.contextAsPercentage` defaults to `false`. Opting in replaces only the numerator with percentage used to one decimal place, e.g. `24.7%/500k`. Keep context distinct from the subscription usage bar.
+- Reload settings at installation boundaries (enable and session start) before deriving footer state, so the first render uses the effective configuration. Ordinary refreshes use the cached configuration and must not reload settings.
 - Unknown token usage is `?/500k` in either mode; absent context usage is `?`. Never present unknown usage as zero.
 
 ## Git contract
@@ -66,7 +67,7 @@ Display only the selected provider's shortest applicable window. Subscription us
 | Kimi Coding (`kimi-coding`) | Shortest available window; accepts used or remaining counts and week/month durations |
 | OpenCode Go (`opencode-go`) | Shortest rolling/weekly/monthly window |
 
-Reuse Pi's selected-provider credentials. Copilot uses the GitHub login token from Pi's configured agent directory or `COPILOT_GITHUB_TOKEN`. Pi 1.0.3 does not include Gemini CLI in its built-in model catalog. Do not poll custom proxy endpoints or make model requests to obtain usage.
+Reuse Pi's selected-provider credentials. Copilot uses the saved OAuth GitHub login token when applicable; otherwise it uses the credentials resolved by Pi, which can include `COPILOT_GITHUB_TOKEN`. Ambient environment tokens do not override Pi's resolved credentials. Pi 1.0.3 does not include Gemini CLI in its built-in model catalog. Do not poll custom proxy endpoints or make model requests to obtain usage.
 
 ### Refresh and failure behavior
 
@@ -87,7 +88,7 @@ The comparison with [mtrojnar/pi-usage](https://github.com/mtrojnar/pi-usage) in
 
 ## Local development
 
-Requires Node.js >=22.19.0. Local dependencies pin Pi 1.0.3; compatibility CI tests Pi 1.0.3 and 1.1.0 on Node.js 22.19.0. Provider requests are mocked. These are tested versions, not a guarantee for every intervening or future release.
+Requires Node.js >=22.19.0. Local dependencies pin Pi 1.0.3; compatibility CI is configured to test Pi 1.0.3, 1.1.0, and 1.3.0 on Node.js 22.19.0. Provider requests are mocked. These are tested versions, not a guarantee for every intervening or future release.
 
 ```bash
 npm ci
@@ -133,20 +134,47 @@ Emit after this extension's `session_start` handler has run; events before start
 
 The latest explicit action wins: `/minfooter on/off` changes the current footer and saves the preference, while this event changes only the current session. Normal refreshes never undo the choice. A new session or extension reload starts from the saved preference.
 
-Disabling restores Pi's default footer only if we still own the active footer; otherwise it leaves the active footer untouched. Enabling explicitly installs our footer and may replace another extension's footer; repeated enables while we own it do nothing. Neither action restores a previous extension's footer. A coordinating extension must choose the active footer—there is no priority stack or automatic reactivation.
+Disabling restores Pi's default footer only if we still own the active footer; otherwise it leaves the active footer untouched. Enabling explicitly installs our footer and may replace another extension's footer. Repeated enable events while we own it do nothing; `/minfooter on` reloads settings and reinstalls the footer. Neither action restores a previous extension's footer. A coordinating extension must choose the active footer—there is no priority stack or automatic reactivation.
+
+#### Session-only usage control
+
+Control subscription usage independently of footer visibility:
+
+```typescript
+pi.events.emit("pi-minimal-footer:set-usage-enabled", { enabled: false }); // suppress usage
+pi.events.emit("pi-minimal-footer:set-usage-enabled", { enabled: true });  // enable usage
+pi.events.emit("pi-minimal-footer:set-usage-enabled", { enabled: null });  // restore saved showUsage
+```
+
+- A boolean overrides `minFooter.showUsage`; `null` clears the override. No settings writes or notifications.
+- Emit after this extension's `session_start` handler. Events outside an active session, missing `enabled`, and values other than boolean or `null` are ignored. Repeated override values do nothing.
+- Disabling clears cached usage, cancels pending requests, and stops timers. Late results and passive provider updates cannot revive usage.
+- Enabling selects usage only while the footer is enabled, owns a live renderer, and runs in TUI mode. It never installs or replaces a footer.
+- Changes request a redraw without reinstalling the renderer or refreshing Git.
+- The override survives footer toggles and reinstallation, but resets on session start/shutdown and extension reload. Clearing it uses the cached setting; settings reload at the normal installation boundaries.
+- No automatic host detection. A coordinating extension can suppress duplicate quota reporting, for example when a terminal plugin already displays usage.
 
 ### Code map
 
-- `extensions/index.ts`: settings, plain state updates, active-footer refresh gate, layout, footer lifecycle, and `/minfooter`.
+- `extensions/index.ts`: Pi events/commands, footer ownership, model/context formatting, theme application, and module wiring.
+- `extensions/lib/footer-settings.ts`: defaults, validation, and settings persistence; preserves unrelated preferences.
+- `extensions/lib/footer-layout.ts`: width allocation and truncation of supplied segments, independent of Pi lifecycle and theme selection.
+- `extensions/lib/git-status.ts`: Git divergence state, stale-result protection, highlight pulses, local polling, and optional fetch/cancellation. The active renderer starts/stops this lifecycle; superseded renderer disposal cannot stop its replacement.
 - `extensions/lib/usage-limits.ts`: usage refresh, cache, cancellation, and bar/reset rendering.
-- `extensions/lib/usage-providers.ts`: authentication, endpoint selection, and response normalization.
-- `tests/`: lifecycle/layout regressions, Git highlighting with a temporary repository, and usage parsing tests.
+- `extensions/lib/usage-providers.ts`: authentication, endpoint selection, and named private provider parsers. `parseUsageWindows` gates supported endpoints, dispatches parsing with an explicit snapshot, and centrally distinguishes valid windows, absence, and malformed responses.
+- `tests/min-footer.test.mjs`: settings, session lifecycle, and context-format integration coverage.
+- `tests/layout.test.mjs`: layout, ANSI/Unicode, and usage bar/reset formatting.
+- `tests/git.test.mjs`: fetch jitter, live ownership, stale queries across refresh/restart/directory changes, and Git highlighting with a temporary repository.
+- `tests/usage-lifecycle.test.mjs`: usage authentication, polling, cancellation, passive updates, and provider integration.
+- `tests/helpers/footer-fixture.mjs`: shared real-loader/context helpers and per-process isolated agent/home setup, default settings resets, and teardown.
+- `tests/usage-parsing.test.mjs`: provider parsing.
+- `tests/persistence-order.test.mjs`: real `AgentSession` message persistence and post-persistence footer usage.
 
 Settings live under `minFooter` in Pi's configured agent directory. Read them at session start or explicit toggle; ordinary refreshes use cached settings. Preserve unrelated settings on writes. Only install the footer in interactive terminal mode.
 
 ### Checking changes
 
-Run `npm run check` and `npm test` for behavior changes. Cover relevant cases:
+Run `npm run check` and `npm test` for behavior changes. Each test file can also run independently, e.g. `node --test tests/git.test.mjs`. Keep the default per-file process isolation: the shared footer fixture sets isolated agent/home environment paths before importing Pi and resets settings and `Math.random` for each test. Provider requests are mocked; numeric context formatting remains real-loader integration coverage. Cover relevant cases:
 
 - Layout: narrow widths, ANSI/wide Unicode, field priority, and separator modes.
 - Git: divergence, synced styling, highlight expiry/restart, and user submissions versus tool turns.