[xinspark]

Six panel improvements, plus three defects found while exercising them on a live profile. Everything stays inside the plugin's existing shape: one client file, CSS in the same template string, both dictionaries, labelled ctx.effect() calls, no new dependencies.

What changed

1. All-time range, no artificial span limit

rangeFor('all') maps to {from: 0, to: now} with fill: false, so the all-time view only buckets days that carry data and never approaches MAX_BUCKETS. The custom range no longer advertises a "30 days max" limit: the only real bound is the bucket guard, and the hint now says so. fill stays on for the rolling presets, where empty days are meaningful.

2. Model filter: candidates no longer collapse, and survive records without a provider

Two separate defects:

• The host collected seenModels after applying the model filter, so the response only offered the models already selected; picking one hid the rest.
• The client composed provider + '/' + model unconditionally, while the host key is the bare model when a record has no provider. Selecting such a candidate matched nothing, and the panel silently showed zero.

The response now carries the host's composed key for every model and the client uses it verbatim, so both sides share one definition.

3. Popovers are no longer clipped by the settings panel

.tsd-popover was absolutely positioned inside a panel with overflow: hidden. A small useFixedPanel(anchorRef, open, width) hook measures the anchor, positions the panel fixed, flips it upward when there is no room below, and caps maxHeight. The model filter, the custom date range and the new currency menu all use it.

4. Currency switch for the reference cost (CNY / USD, fixed 1 USD = 7 CNY)

• DEFAULT_PRICES holds DeepSeek's USD list (0.27 / 1.10 / 0.07) but was printed with a ¥. The table is now explicitly USD-based and CNY display multiplies by 7, which lands on DeepSeek's published CNY list — so this also corrects the previous numbers, which were 7× too low.
• Conversion happens at the output boundary in query (costOf, daily, byModel, total, heatmap); the price table itself is never rewritten, and hasPrice still decides priced vs unpriced.
• The switcher lives in the cost card's value row (symbol + chevron). The symbol has exactly one owner: costDigits returns digits only, since two owners produced ¥ ¥14.78. The menu states the fixed rate.
• The choice is remembered per browser via localStorage as a display preference; it never touches the plugin configuration.

5. Model-share card (6th KPI)

A 10 px pill bar with an 11 px caption (deepseek-flash 53.5%), as a normal .tsd-cards item. Colours come from families the theme actually ships (--dsw-static-{deepseek,green,amber,red}-*); "others" is tinted deepseek-300 rather than neutral grey, which reads as disabled on a dark card. Per-segment detail is a fixed tooltip (the heatmap's technique) instead of a native title, whose black box covered the adjacent card.

6. Artwork and plugin-page metadata

• package.json#icon plus icon.svg (transparent 36×36, diagonal #67C7FE → #3F77D8).
• locale/{en,zh}.json carrying meta.title / meta.description and the matching ./locale/*.json export: without them the plugin page falls back to the bare package name and the truncated English description.
• A settings-nav glyph, because settings.section cannot carry an icon: the runtime's navIcon(id) is a closed list and returns a gear for any other id. The patch only adds a data-tsd-nav attribute and paints the glyph with ::before + mask; the React-owned <svg> is never replaced (doing so makes React's removeChild throw when the panel unmounts). If the row cannot be identified, nothing happens. This block should be deleted once settings.section accepts an icon.

Verification

• npm run build, node --check lib/client/index.js, npm test — 83 pass, 0 fail (6 new host tests for the filter and currency paths).
• Installed into a live profile and exercised by hand: every range preset, empty-provider filtering, both currencies, the share card, the artwork.
• There is no client test harness in this repo, so client-only changes are covered by manual checks only.

[xinspark]

@ruanbw 一个发布上的缺口想确认下：v0.3.0 已经合进 main、打了 tag、Release 也出了，但 npm 上的 dsh-plugin-usage 还停在 0.2.2。

README 写的两种装法（dsh plugin add dsh-plugin-usage、设置 → 插件 → 添加插件）走的都是 npm，所以照文档装还是旧构建，这一版的「全部」范围、货币切换、模型占比卡、图标和插件页文案都不会出现。

release.yml 目前只到「校验 tag → 构建 → 测试 → 建 Release」，没有发布步骤。你方便的话，本地 npm publish 一次，或者在 release.yml 里加一步 npm publish + NPM_TOKEN，我都可以配合。如果卡的是 npm 权限，把我加成包的合作者也行——发之前我会先跟你确认，版本号 / tag / dist-tag 的策略我不动。不着急。

[ruanbw]

@xinspark 已经发布到 npm 官方源（v0.3.0），并将 npm 页面地址（https://www.npmjs.com/package/dsh-plugin-usage）加到了仓库的 Website/URL 中。感谢提醒！

[xinspark]

@ruanbw 谢谢，确认过了：npm 上 0.3.0 的构建与 v0.3.0 源码一致（拉下来和本地重新构建逐行比对，只有内联 sourcemap 的路径不同），我这边已经改用 npm 版本安装。另外我按 awesome-dsh-plugin 的格式提了一条收录（#7986），条目里引用的就是这个仓库。