Usage Pace 0.4.4 — macOS sidebar footer fix

Patch release for the compact strip in bb 0.47's macOS desktop app.

Fixes

• The strip uses bb's supported sidebar footer API. Its own footer icon opens a bordered, scrollable card above bb's footer buttons. The strip no longer inserts into bb's footer markup, where the desktop app's fixed 48px row hid account rows and pushed controls below the window.
• Opens once, not after every refresh. With showStrip enabled, the card opens at startup. bb allows one footer disclosure open at a time: opening Provider usage closes the strip; the Usage Pace icon brings it back. Background updates never take over the open card. bb does not remember the open disclosure across reloads.
• Refresh and reset reads follow the right lifetimes. Quota polling every five minutes while the page is visible, focus/visibility refreshes, and refresh after an exhausted account's reset passes continue with the strip closed. Saved-reset reads run only while the strip or details dialog is open, sharing the same inventory and badges.

showStrip remains off by default. Reload the app UI after changing it so bb can add or remove the registered footer item. The dialog, Provider usage pace ticks/per-tab errors/hidden providers, server-only filtering, CLI, and read-only reset behavior are unchanged. Release artifacts retain the BB 0.44.0 / SDK 0.5.29 toolchain; minimum requirements and dependency pins are unchanged.

Verification

• The same startup regression failed on pristine 0.4.3 and passed after the fix: one supported disclosure, opened once, with no injection into bb's footer. All five new lifecycle tests pass, including off/no registration, closed-card quota refresh, passed-reset refresh, and saved-reset reads only while the actual strip or dialog is open.
• All 411 Vitest tests, 3 token-total tests, TypeScript, and release validation passed and were rerun before merging. Comment policy passed across 113 files with zero violations; all 13 policy regression tests passed. Staged policy, the ordinary pre-commit hook, and redacted secret scanning passed during preparation.
• Production-only rebuilds and release validation passed with BB 0.44.0 / SDK 0.5.29 and BB's bundled npm 11.16.0, including version/SDK metadata, host digest, and isolated backend/host smoke loading. No provider requests were made by release validation.
• A throwaway bb-app 0.47.1 instance with synthetic example.test usage reproduced the macOS layout failure on 0.4.3. The actual release bundle passed at 1440×900 and 1440×600, in both stubbed macOS desktop mode and normal browser tabs: all five strip rows and all footer controls are inside the window and centre-hit-testable. Opening Provider usage closes the strip; the Usage Pace icon reopens it. The bridge stub leaves missing numeric inset fields undefined so bb uses its shipped defaults. No bb code or layout CSS is patched. The temporary instance and its data were removed afterwards.
• The existing component/CSS fixture also passed server/all-host strip widths 172/212/252px and desktop/mobile dialogs 1200/375px, preserving stale-account explanations, partial pools, saved-reset badges, and server-only reset targeting without horizontal overflow.
• PR CI, resulting-main CI, and release-tag CI passed. The annotated v0.4.4 tag points to merge commit 842ae6175dbe7f6a7773b1b2f892a881fbfebad5, whose tree exactly matches reviewed and tested PR head 3a5cec7891c3a98548cd147136152a6bc74da16e. GitHub Actions lists no runs for those SHAs; Woodpecker results were verified through commit statuses.
• Not yet verified: installation or upgrade of 0.4.4 on either real bb server, native AppKit behavior, or real provider acceptance. Before/after measurements and screenshots are recorded in sidebar footer verification. Only synthetic identities and example.test addresses are used.

New installations

bb plugin install 'git:https://github.com/scowalt/bb-plugin-usage-pace.git@v0.4.4'
bb plugin config usage-pace set showStrip true

Reload the app UI to show the optional card. Use @^0.4.4 instead of the exact tag to track compatible releases.

Upgrades

Inspect the installed source first:

bb plugin source usage-pace

For a branch-tracking install whose branch contains 0.4.4, or a release-range install admitting this tag, update in place and preserve settings:

bb plugin update usage-pace

Exact tags and commits do not advance to a newer tag. Moving a pinned install, or changing an existing install to a tag or range, requires removal first. Removal deletes settings, secrets, and schedules. Record your configuration and restore it after reinstalling:

bb plugin config usage-pace
bb plugin remove usage-pace
bb plugin install 'git:https://github.com/scowalt/bb-plugin-usage-pace.git@v0.4.4'

Use @^0.4.4 in the last command for compatible-release tracking. Do not install over an existing managed install. Reload the app UI after upgrading.

Publishing this release does not install, update, reload, or reconfigure plugins on either live bb server. The user's old checkout and other repositories remain untouched.

PR #10 · Full changelog