0.0.10: Keep quota hover width stable beside the filename footer

Reserve the maximum terminal-cell width of the quota summary and reset countdowns. Switching to shorter hover text otherwise shifts the boundary beside the flex-growing filename, repeatedly triggering mouseout and mouseover even with a stationary pointer.

Keep updates event-driven without timers or polling. Verified stable hover across repeated OpenTUI renders, restoration on exit to the filename, repository checks, and whitespace checks.

0.0.9: Preserve quota text identity across hover transitions

Update a stable runtime JSX text node through reactive content and theme getters. Replacing the hovered renderable could suppress OpenTUI mouseout events when the pointer exited before the next render, leaving reset countdowns stuck on screen.

Keep hover updates event-driven without timers or polling and avoid redundant hover containers. Verified repository checks and focused runtime mouse-exit behavior.

0.0.8: Show relative quota reset countdowns

Render hovered quota reset values as durations from the current time, using in H:MM or in Dd H:MM formats. Recalculate only during the hover render so the footer does not start a repeating timer or polling loop. Update the README example to document the current overlay format.

0.0.7: Refresh quota on focused session turns

Remove periodic quota polling and refresh at the start and end of the focused TUI session's execution. Ignore turn events from background or unfocused sessions while preserving startup, account, model, and location refresh triggers.

0.0.6: Harden usage quota TUI integration

Route quota RPC calls to the active location and refresh on location or local model changes. Keep installed raw TSX hover and theme rendering reactive, prevent stale updates after cleanup, and narrow the RPC contract to emitted quota values. Document hover behavior and ignore Serena metadata in Prettier.

0.0.5: Prevent unchanged usage refresh flicker

Keep the existing footer state while quota refreshes are in flight and skip state writes when the derived status and quota snapshots are unchanged. Ignore observedAt during comparison because it changes on every fetch without changing the displayed quota data.

0.0.4

Keep installed usage footer reactive

Git-installed TUI sources use runtime JSX, which evaluates Show conditions and For inputs at mount. Pass reactive getters to Solid's control-flow components so the initial quota fetch updates the home footer, provider changes hide or reveal it, and credential switches update the displayed account without remounting the footer.

0.0.3: Show quota during model initialization

Allow the footer status to render while OpenCode is still resolving the initial home-screen model. Keep the provider filter reactive so the OpenAI quota remains hidden as soon as a non-OpenAI model is selected.

0.0.2: Route usage footer by selected provider

Render the quota in the home footer on the home route and in the prompt footer elsewhere, while keeping the two placements mutually exclusive. Refresh when the selected model changes provider and hide the OpenAI quota for non-OpenAI models so stale usage is not shown for OpenCode Zen or other providers.

0.0.1: Simplify quota retrieval and separate account from usage values

Read the single supported OpenAI provider directly instead of maintaining an adapter registry, parallel aggregation, and duplicate error handling. Construct the RPC response at its boundary while preserving quota data, validation errors, cancellation, and cleanup.

Use native Map.groupBy without copied group metadata. Remove redundant date and width helpers and the finite-number guard already enforced by Zod. Add a middle-dot separator between the account label and quota windows, and update the README example.

Verification: ESLint, TypeScript, tracked-file Prettier checks, package dry-run, and git diff --check passed. In-memory comparisons matched 28 server and 31 footer scenarios before the requested separator change; a focused formatting assertion confirmed that change. The full check script is blocked by a pre-existing permission error reading .serena/project.yml.