@rayadesu/dsh-billing 0.3.13 → 0.3.14

package/AGENTS.md

@@ -65,7 +65,7 @@ cordis.patch.yml         DSH profile bundle 补丁层：挂载 llm-billing + ui-
 - **密钥不进仓库**：`DEEPSEEK_API_KEY` 等一律由用户环境或凭据 seam 提供，仓库不含真实值。
 - **README 双语**：每个 README 遵循 DSH 结构 `README.md`(EN) + `README.zh.md`(ZH) +
   `README.i18n.yaml`（记录两文件 git blob hash，改动后需更新）。
-- **版本对齐**：根 bundle 与两个包统一版本号（当前 0.3.13），`pnpm-lock.yaml` 随依赖变更更新。
+- **版本对齐**：根 bundle 与两个包统一版本号（当前 0.3.14），`pnpm-lock.yaml` 随依赖变更更新。
 - **提交与发布流程**：见 `.agents/skills/dsh-release/SKILL.md` —— 阶段 A（改代码 → 按档位校验/打包 →
   本地 pack 安装 → 交用户验证）**不提交**，改动留在工作区；用户说「发布」进入阶段 B 才 bump 版本、
   **按类型分别提交**、推送、发 npm 与 GitHub Release。

package/README.i18n.yaml

@@ -2,5 +2,5 @@
 # last confirmed-consistent state. Both languages carry equal authority; after
 # editing either side, bring the other along and re-record both hashes with:
 #   git hash-object README.md README.zh.md
-README.md: fee1f7f0233cb3b78b0416bfd17e507875479a8b
-README.zh.md: 568258156c786048433fe8b58fe6999831c7c50e
+README.md: 1e65c00d536d0c589976b3bbbe2c551afc54957b
+README.zh.md: b38c56782db1edd4ed3d5d3ab75a463f6996d16a

package/README.md

@@ -9,29 +9,29 @@ A [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) plugin tha
 ## What it shows
 
 - **Session-header badge** — two lines: remaining balance (`剩余金额：¥X`, the panel's headline without its `API` prefix — the chip is narrow) and this conversation's billed spend (`本会话花费：¥X`, its own work plus every subagent session it delegated, worded exactly as the panel labels it).
-- **Detail panel** — the remaining amount; today's billed token count next to today's all-session spend (`今日 Token` / `今日花费`, one row; the count is DSH's compact notation with its own unit — `12.2K tok`, followed by the day's cache-hit share as a bare, unparenthesized percentage, rendered by DSH's own hit-rate rule: an integer percent that grows decimals only as far as a partial hit needs to stay below 100, and none at all when the day billed no prompt-side input); directly under that row, today's two bucket detail lines — tokens on top, costs below, each on its own with its natural ` · ` spacing (no column alignment between them), in the per-model breakdown line's typography but on the third section's row spacing (the today session-spend ranking's tight 6px rhythm); every spend amount renders at **three significant digits** (`¥9.58`) but never finer than four decimals — an amount below ¥0.0001 reads `¥0` — while the balance line alone keeps four decimals; this conversation's spend on its own line below them (`本会话花费` — this session plus the subagent sessions it delegated, per-model rows included; with this conversation's share of today trailing it, bare and unparenthesized (`¥X`), rendered **only when the conversation did not start today** — the session's own creation day decides (the delegated read reports `crossedDay`), not a comparison of the two amounts, because the live session figure and the 60-second-cached ranking row routinely differ mid-turn; one priced row per model (`未缓存输入 ¥X · 缓存读取 ¥Y · 输出 ¥Z` — DSH's own bucket wording and row order), plus a manual refresh action and a spend disclaimer on the `?` button (one line of estimate scope, then a line stating that the amounts include the subagent sessions this session delegated, then a line naming the amount trailing the session figure as this conversation's spend today, and the running plugin version as the last line, e.g. `v0.3.13`). The panel ends with a **today session-spend ranking**: sessions sorted by today's spend, highest first — one row per conversation, since each subagent session's spend is merged into the row of the session that delegated it (names come from the log's Chinese titles and follow renames automatically; at most the top 10 rows, with a "…N more sessions" hint).
+- **Detail panel** — the remaining amount with today's consumption measured from the balance series after it (see *How session spend is computed*); today's billed token count next to today's all-session spend (`今日 Token` / `今日花费`, one row; the count is DSH's compact notation with its own unit — `12.2K tok`, followed by the day's cache-hit share as a bare, unparenthesized percentage, rendered by DSH's own hit-rate rule: an integer percent that grows decimals only as far as a partial hit needs to stay below 100, and none at all when the day billed no prompt-side input); directly under that row, today's two bucket detail lines — tokens on top, costs below, each on its own with its natural ` · ` spacing (no column alignment between them), in the per-model breakdown line's typography but on the third section's row spacing (the today session-spend ranking's tight 6px rhythm); every spend amount renders at **three significant digits** (`¥9.58`) but never finer than four decimals — an amount below ¥0.0001 reads `¥0` — while the balance line alone keeps four decimals; this conversation's spend on its own line below them (`本会话花费` — this session plus the subagent sessions it delegated, per-model rows included; with this conversation's share of today trailing it, bare and unparenthesized (`¥X`), rendered **only when the conversation did not start today** — the session's own creation day decides (the delegated read reports `crossedDay`), not a comparison of the two amounts, because the live session figure and the 60-second-cached ranking row routinely differ mid-turn; one priced row per model (`未缓存输入 ¥X · 缓存读取 ¥Y · 输出 ¥Z` — DSH's own bucket wording and row order), plus a manual refresh action and a spend disclaimer on the `?` button (one line of estimate scope, then a line stating that the amounts include the subagent sessions this session delegated, then a line naming the amount trailing the session figure as this conversation's spend today, and the running plugin version as the last line, e.g. `v0.3.13`). The panel ends with a **today session-spend ranking**: sessions sorted by today's spend, highest first — one row per conversation, since each subagent session's spend is merged into the row of the session that delegated it (names come from the log's Chinese titles and follow renames automatically; at most the top 10 rows, with a "…N more sessions" hint).
 - **Turn cost amount** — each completed turn's closing message shows a plain static `¥X` at the **end** of the actions row, after the clock: non-interactive (no icon, no "cost" word, no card), its typography replicates the clock text (13px secondary tier, tertiary tone, nowrap), and it is **always visible** (not hover-revealed like the clock text — the row's own hover reveal shows both together); turns without DeepSeek usage (zero cost) or failed loads stay hidden.
 - **Failures and empty states** — a session or day without priced usage shows "no usage recorded" instead of a fabricated figure; a missing key, rejected credential, or transport error renders a muted "Balance unavailable" whose tooltip carries the Remote's own error message.
 
 ## Data update mechanics
 
 - **Session spend follows the conversation** — the host prices every committed event into a per-session projection (`billingTodaySpend`) and pushes it to the browser, so **this session's own spend** updates live with no Remote call; the Remote read remains the fallback when the projection registry is absent, and `billing/getDelegatedSpend` adds the subagent sessions this session delegated (fetched on mount, on refresh, and when a turn settles) so the amount shown is the whole conversation's. **Today's spend** is recomputed on turn settle (one shared scan serves the aggregate, the ranking, and the delegated subtotal), and the parenthesized today share on that same session line reads that same ranking fetch (no extra request, at the cost of moving with it); each turn's cost comes from **one batch fetch per session** instead of one call per rendered message.
-- **Balance is cached, not polled** — the host reuses one `/user/balance` snapshot for 15 seconds (manual refresh forces a fresh one) and caps each request at 5 seconds; the browser keeps the last settled value so a session switch renders the amount immediately and revalidates in the background. There is still no polling.
+- **Balance is cached and polled** — the host reuses one `/user/balance` snapshot for 15 seconds (manual refresh forces a fresh one) and caps each request at 5 seconds; the browser keeps the last settled value so a session switch renders the amount immediately and revalidates in the background, and polls every 5 minutes while the page is visible (paused while the document is hidden, refreshed once on return) — the balance-series consumption below is measured from the first balance each local day samples, so that cadence is its resolution.
 - **Old values survive refreshes** — a failed refresh keeps the last good value instead of blanking it.
 
 ## Preview
 
 A real session: the session-header badge and the open detail panel:
 
-<img width="1200" alt="Billing plugin overview: session header badge and the open detail panel (remaining amount, today's tokens and spend, this session's spend, per-model breakdown, today's session ranking)" src="preview-overview.png" />
+![Billing plugin overview: session header badge and the open detail panel (remaining amount, today's tokens and spend, this session's spend, per-model breakdown, today's session ranking)](preview-overview.png)
 
 Close-up of the detail panel — the `API 剩余金额` figure, `今日 Token` and `今日花费`, `本会话花费` (with its parenthesized today share once the session crossed a day), the per-model breakdown (`未缓存输入 · 缓存读取 · 输出`), and the today session-spend ranking:
 
-<img width="496" alt="Detail panel close-up: API remaining amount, today's tokens and spend, this session's spend with its parenthesized today share, the uncached-input / cached-input / output breakdown, and the today session ranking" src="preview-detail.png" />
+![Detail panel close-up: API remaining amount, today's tokens and spend, this session's spend with its parenthesized today share, the uncached-input / cached-input / output breakdown, and the today session ranking](preview-detail.png)
 
 Close-up of the turn-cost amount — the static `¥` amount at the end of the actions row, after the clock:
 
-<img width="640" alt="Turn-cost amount close-up: the static ¥ amount at the end of the actions row, after the clock" src="preview-turn-cost.png" />
+![Turn-cost amount close-up: the static ¥ amount at the end of the actions row, after the clock](preview-turn-cost.png)
 
 
 ## Package layout
@@ -267,6 +267,8 @@ Both packages ship sane defaults; everything below is optional.
 - **Today session ranking** aggregates today's spend per session with the same rules (a cross-day session counts only today's part), sorted descending; names come from the log's latest `session/title` event (the auto-generated Chinese title or a user rename). It ranks **conversations**: a subagent session (DSH stamps its header with `origin: 'subagent'` and a `delegationDepth`; a user fork carries neither) is merged into the row of the top-level session that delegated it, so one row is one conversation. Each row reports `total` (the conversation's whole day, subagents included) plus `ownTotal` (that session's own spend) — the panel's trailing share reads `ownTotal`, and the day's aggregate total is unchanged by the regrouping.
 - Models without a rate row are not priced (the built-in table covers the DSH `llm-deepseek` catalog — V4.1 Flash `deepseek-flash`, V4 Flash, V4 Pro, V4 Flash Vision Exp — plus the retired `deepseek-v4.1-flash-expires-on-0910` preview id and the MiMo-V2.5 series; every flash-series route shares the same pair). Each sample takes the rate revision in effect at its own timestamp: the base schedule is the DeepSeek pricing effective **August 17**; the **flash series** (V4.1 Flash, V4 Flash, V4 Flash Vision Exp, and the retired id) was re-priced effective **September 10, 12:00 Beijing time** to off-peak 0.02 / 1.0 / 4.0 CNY per 1M tokens with peak at twice those prices — samples from before that instant, the V4.1 Flash route's own earlier usage included, keep the superseded rates; the **V4 Pro** route is announced to switch to V4.1 Flash and its rates on **September 14, 12:00 Beijing time**; the MiMo-V2.5 series is untouched. The weekend-off-peak rule (weekends billed at off-peak prices all day) follows the adjustment effective **August 23**.
 
+- **The balance-series "today's consumption"** (the figure right after `API 剩余金额`) is pure account arithmetic and never enters the token pricing above: the first balance queried on the local calendar day − the current balance + the day's detected top-ups (an increase rounds **up to the next ¥10 step**, because the provider only tops up in round tens). It is the caliber of the `balanceinfo` program this plugin mirrors, and it is deliberately a separate figure from the priced 今日花费 — spend from another client, or from before this browser was opened, shows up only here; the two figures disagreeing is normal. The day record lives in this browser's `localStorage` (key `dsh.billing.balance-day.v1`), survives reloads and `dsh` restarts, rolls over on the **local** calendar day (the browser's day, not the host's Beijing day key), is sampled on mount, on session switch, on the manual refresh, and every 5 minutes while the page is visible, renders only once the day holds a sample, and is not shared between clients. Details in [`packages/ui-billing/README.md`](packages/ui-billing/README.md).
+
 ## Known limitations
 
 - **Priced rows only** — the session, turn, and today spends only price models that have a `billing.models` row (today's token count reads those same rows, so it covers priced models only).
@@ -276,7 +278,7 @@ Both packages ship sane defaults; everything below is optional.
 - **A merged row can be untitled** — a subagent whose parent session is outside the scan (a deleted or archived parent log, for instance) is still attributed to the parent id its own header names, but that log is never read, so the merged row shows the untitled fallback until the parent is scanned.
 - **Ranking capped at 10** — the panel shows at most the top 10 conversations (the host's subagent roll-up runs first, so one row is one conversation), with a "…N more sessions" hint.
 - **Turn cost needs a finalized closing message** — interrupted turns have no actions row, so no turn cost; cold sessions served straight from the projection cache may rank with an "Untitled" name until their log is read again.
-- **Balance is TTL-cached** — the host reuses one snapshot for up to 15 seconds and each request aborts after 5 seconds; spending from another client does not move the shown value until the TTL expires, a manual refresh, or a browser reload (there is no polling).
+- **Balance is up to 15s stale between polls** — the host reuses one snapshot for up to 15 seconds and each request aborts after 5 seconds; spending from another client moves the shown value at the next poll (5 minutes while the page is visible, none while it is hidden), at a manual refresh, or at a browser reload.
 - **Estimate, not a promise** — the session spend prices tokens at official rates; the provider's actual billing prevails.
 
 ## License

package/README.zh.md

@@ -9,29 +9,29 @@
 ## 显示什么
 
 - **会话头部徽标** —— 两行：剩余余额（`剩余金额：¥X`，是面板标题去掉 `API` 前缀的短版，徽标较窄）＋ 本轮对话的计费花费（`本会话花费：¥X`，含本次对话委派的每个子代理会话，文案与面板完全一致）。
-- **详情面板** —— 剩余金额；今日计费 token 数与今日所有会话合计同一行（`今日 Token` / `今日花费`，token 数按 DSH 的紧凑记数法带自己的单位，如 `12.2K tok`，token 数值后紧跟当天的缓存命中率（裸数字、无括号）——按 DSH 官方命中率规则渲染：整数百分比，只有部分命中会被凑到 100% 时才逐位多留小数；当天没有 prompt 侧输入就不显示）；紧跟该行下面是**今日两行桶明细**——token 在上、花费在下——两行各自成行、各自保持自然的 ` · ` 间距（两行之间不做列对齐），排版沿用下方模型分项那一套，行距用第三部分（今日会话花费排行）那一套紧凑节奏；**面板上所有花费金额都按三位有效数字渲染**（`¥9.58`），但**不细于四位小数**——低于 ¥0.0001 的金额显示 `¥0`；只有余额行保留四位小数；下一行才是本会话花费（`本会话花费`——本会话加上它委派的子代理会话，模型分项同样合并；金额后**只在这段对话不是今天才创建时**才紧跟今日份金额 `¥X`——判定用的是会话自身的创建日（子代理读取给出 `crossedDay`），不再比较两个金额，因为实时的本会话数字与 60 秒缓存的排行行在回合中途本来就会不一致；以及每个模型一行的花费分项（用 DSH 自己的桶名与行序：`未缓存输入 ¥X · 缓存读取 ¥Y · 输出 ¥Z`），外加手动刷新按钮与「?」上的花费说明（一句估算口径，一行说明金额含本会话委派的子代理会话，一行说明紧跟的金额是本次对话今日花费，最后一行顶格是当前插件版本号，如 `v0.3.13`）；面板底部是**今日会话花费排行**：按今日花费从高到低排列的会话列表——一行就是一个对话，子代理会话的花费已并入委派它的那个会话行（会话名取日志中的中文标题，重命名后自动同步；最多显示前 10 条，其余以「…还有 N 个会话」提示）。
+- **详情面板** —— 剩余金额（后跟按余额序列算出的今日消费，见「会话花费是怎么算的」）；今日计费 token 数与今日所有会话合计同一行（`今日 Token` / `今日花费`，token 数按 DSH 的紧凑记数法带自己的单位，如 `12.2K tok`，token 数值后紧跟当天的缓存命中率（裸数字、无括号）——按 DSH 官方命中率规则渲染：整数百分比，只有部分命中会被凑到 100% 时才逐位多留小数；当天没有 prompt 侧输入就不显示）；紧跟该行下面是**今日两行桶明细**——token 在上、花费在下——两行各自成行、各自保持自然的 ` · ` 间距（两行之间不做列对齐），排版沿用下方模型分项那一套，行距用第三部分（今日会话花费排行）那一套紧凑节奏；**面板上所有花费金额都按三位有效数字渲染**（`¥9.58`），但**不细于四位小数**——低于 ¥0.0001 的金额显示 `¥0`；只有余额行保留四位小数；下一行才是本会话花费（`本会话花费`——本会话加上它委派的子代理会话，模型分项同样合并；金额后**只在这段对话不是今天才创建时**才紧跟今日份金额 `¥X`——判定用的是会话自身的创建日（子代理读取给出 `crossedDay`），不再比较两个金额，因为实时的本会话数字与 60 秒缓存的排行行在回合中途本来就会不一致；以及每个模型一行的花费分项（用 DSH 自己的桶名与行序：`未缓存输入 ¥X · 缓存读取 ¥Y · 输出 ¥Z`），外加手动刷新按钮与「?」上的花费说明（一句估算口径，一行说明金额含本会话委派的子代理会话，一行说明紧跟的金额是本次对话今日花费，最后一行顶格是当前插件版本号，如 `v0.3.13`）；面板底部是**今日会话花费排行**：按今日花费从高到低排列的会话列表——一行就是一个对话，子代理会话的花费已并入委派它的那个会话行（会话名取日志中的中文标题，重命名后自动同步；最多显示前 10 条，其余以「…还有 N 个会话」提示）。
 - **本轮花费金额** —— 每条已完成回合的收尾消息操作行**行尾**（时钟之后）显示纯静态的 `¥X`：不可点击、无图标、无「花费」字样、不弹卡片，字体样式逐项复刻时钟文本（13px 次级字号、tertiary 色、nowrap），并且**始终显示**（不随悬停隐藏，与时钟文本一致——整行的悬停显隐规则让两者同进退）；回合没有 DeepSeek 用量（花费为 0）或加载失败时不显示。
 - **失败与空态** —— 会话或今日没有可计价消耗时显示「暂无消耗记录」而不是编造数字；未配置 key、凭据被拒或传输错误时显示弱化的「额度不可用」，其提示携带 Remote 自己的错误信息。
 
 ## 数据更新机制
 
 - **会话花费自动跟随** —— 主机端把每条已提交事件计价进每会话投影（`billingTodaySpend`）并推送给浏览器，**本会话自身的花费**因此零 Remote 调用、实时更新；投影注册表不存在时回退到 Remote 读取，而 `billing/getDelegatedSpend` 再把本会话委派的子代理会话加上去（挂载时、手动刷新时与回合结束时各拉一次），所以显示的是整次对话的金额。**今日花费**（与同一行的**今日 Token**）在回合结束时重算（聚合、排行与子代理小计共用同一次扫描），本会话花费行紧跟的今日份金额也来自这次排行读取（不额外发请求，代价是与排行同进同退）；每条消息的行尾金额来自**每会话一次批量拉取**，不再逐条消息各发一次请求。
-- **额度有缓存、但不轮询** —— 主机端 15 秒内复用同一份 `/user/balance` 快照（手动刷新强制取新），单次请求 5 秒超时；浏览器保留最后一次结果，切会话时立即渲染旧值并在后台校验。仍然**没有轮询**。
+- **额度有缓存、可见时每 5 分钟轮询** —— 主机端 15 秒内复用同一份 `/user/balance` 快照（手动刷新强制取新），单次请求 5 秒超时；浏览器保留最后一次结果，切会话时立即渲染旧值并在后台校验。此外**页面可见时每 5 分钟轮询一次**（页面隐藏则暂停，回到前台立刻补一次）——下面那条「余额口径的今日消费」以当天第一次采样到的余额为基准，这个节奏就是它的分辨率。
 - **刷新期间旧值保留** —— 刷新失败保留上一次有效值，不会清空。
 
 ## 显示样式
 
 真实会话中的会话头部徽标与展开的详情面板：
 
-<img width="1200" alt="计费插件总览：会话头部徽标与详情面板（剩余金额、今日 Token 与今日花费、本会话花费、按模型分项与今日会话花费排行）" src="preview-overview.png" />
+![计费插件总览：会话头部徽标与详情面板（剩余金额、今日 Token 与今日花费、本会话花费、按模型分项与今日会话花费排行）](preview-overview.png)
 
 详情面板特写 —— `API 剩余金额`、`今日 Token` 与 `今日花费`、`本会话花费`（跨天时含括号内的今日份金额）、按模型分项（`未缓存输入 · 缓存读取 · 输出`）与今日会话花费排行：
 
-<img width="496" alt="详情面板特写：API 剩余金额、今日 Token 与今日花费、本会话花费（含括号内的今日份金额）、未缓存输入/缓存读取/输出分项与今日会话花费排行" src="preview-detail.png" />
+![详情面板特写：API 剩余金额、今日 Token 与今日花费、本会话花费（含括号内的今日份金额）、未缓存输入/缓存读取/输出分项与今日会话花费排行](preview-detail.png)
 
 本轮花费金额特写 —— 操作行行尾（时钟之后）的静态 `¥` 金额：
 
-<img width="640" alt="本轮花费金额特写：操作行行尾的静态金额，位于时钟之后" src="preview-turn-cost.png" />
+![本轮花费金额特写：操作行行尾的静态金额，位于时钟之后](preview-turn-cost.png)
 
 
 ## 包结构
@@ -239,6 +239,8 @@ npm publish   # @rayadesu/dsh-billing bundle（仓库根）
 - **今日会话花费排行**按同一规则按会话汇总今日花费（跨天会话只统计今天的部分），从高到低排序；会话名取日志中最后一条 `session/title` 事件（自动生成的中文标题或用户重命名的新标题）。排行排的是**对话**：子代理会话（DSH 在其 header 上盖 `origin: 'subagent'` 与 `delegationDepth`；用户手动分叉两者都没有）会并入委派它的顶层会话那一行，所以一行就是一个对话。每行给出 `total`（这次对话的整日花费，含子代理）与 `ownTotal`（该会话自己的花费）；面板里紧跟的今日份金额读的是 `ownTotal`，而归组不改变整日合计。
 - 没有费率行的模型不计入（内置价目表覆盖 DSH `llm-deepseek` 目录——V4.1 Flash `deepseek-flash`、V4 Flash、V4 Pro、V4 Flash Vision Exp——外加已退役的 `deepseek-v4.1-flash-expires-on-0910` 预览 id 与 MiMo-V2.5 系列；flash 系列各路由同价）。每份样本取**自身时刻生效的费率版本**：基础价目为 DeepSeek **8 月 17 日实行**的费率；**flash 系列**（V4.1 Flash、V4 Flash、V4 Flash Vision Exp 及退役 id）自 **9 月 10 日 12:00（北京时间）** 起降为谷时 0.02 / 1.0 / 4.0 元每百万 token、峰时为其两倍——该时刻之前的样本（含 V4.1 Flash 路由自身的早先用量的）沿用被取代的旧价；**V4 Pro** 路由公告于 **9 月 14 日 12:00（北京时间）** 改由 V4.1 Flash 服务并按其实施费率计费；MiMo-V2.5 系列不受影响。**周末按低谷价计费**的规则按 **8 月 23 日**生效的调整执行。
 
+- **余额口径的「今日消费」**（`API 剩余金额` 后紧跟的那个数字）是纯账户加减，不参与上面的 token 计价：当天（本地自然日）第一次查询到的余额 − 当前余额 + 当天识别出的充值（余额上涨按 **10 元步进向上取整**，因为厂商只按整十充值）。这条口径与本插件对标的 `balanceinfo` 程序一致，并且**刻意与计价的「今日花费」分成两个数**——别的客户端花的钱、或本浏览器打开前花的钱，只体现在这里；两个数字不一致是正常的。当日记录写在本浏览器的 `localStorage`（键 `dsh.billing.balance-day.v1`），跨页面刷新与 `dsh` 重启保留，按**本地自然日**翻篇（浏览器所在的日，不是宿主的北京日键）；采样发生在挂载、切换会话、手动刷新与页面可见时的 5 分钟轮询，只有当天已经有过一次采样才显示，且不在客户端之间共享。细则见 [`packages/ui-billing/README.zh.md`](packages/ui-billing/README.zh.md)。
+
 ## 已知限制
 
 - **有费率行才计价** —— 会话花费、本轮花费与今日花费（以及同一行的今日 Token：token 数也只统计这些行）只统计价目表（`billing.models`）里有的模型。
@@ -248,7 +250,7 @@ npm publish   # @rayadesu/dsh-billing bundle（仓库根）
 - **子代理小计随回合更新，不逐事件跟进** —— 会话行里本会话自身那部分是实时的（推送投影），子代理那部分来自 `billing/getDelegatedSpend`：挂载、手动刷新与回合结束时各拉一次，并与今日花费共用同一个 60 秒宿主缓存。因此子代理在回合中途烧掉的钱会在下一次读取（回合结束、手动刷新或打开面板）时落到父会话金额上，而不是逐事件实时跳动。
 - **合并行可能显示「未命名」** —— 子代理的父会话不在本次扫描范围内时（例如父日志已被删除或归档），该行仍按 header 里写的父会话 id 归属，但那份日志从未被读取，标题要等父会话被扫描到才显示。
 - **本轮花费只出现在已定稿的收尾消息** —— 中断的回合没有操作行，不显示本轮花费；冷会话（投影缓存直接命中）排行标题可能显示「未命名」，待其日志被重新读取后恢复。
-- **额度带 TTL 缓存** —— 主机端最多复用 15 秒内的同一份快照，单次请求 5 秒超时；账户在其他客户端产生消耗时，界面值要等 TTL 过期、手动刷新或刷新浏览器才变（仍无轮询）。
+- **额度在两次轮询之间最多旧 15 秒** —— 主机端最多复用 15 秒内的同一份快照，单次请求 5 秒超时；账户在其他客户端产生消耗时，界面值会在下一次轮询（页面可见时 5 分钟一次，隐藏时没有轮询）、手动刷新或刷新浏览器时变化。
 - **是估算，不是承诺** —— 会话花费按官方单价对 token 计价；实际计费以服务商为准。
 
 ## 许可证

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rayadesu/dsh-billing",
-  "version": "0.3.13",
+  "version": "0.3.14",
   "description": "DeepSeek Harness billing plugin: account balance and this session's billed spend with a session-header badge.",
   "license": "MIT",
   "repository": {
@@ -40,8 +40,8 @@
     "access": "public"
   },
   "peerDependencies": {
-    "@rayadesu/dsh-client-ui-billing": "^0.3.13",
-    "@rayadesu/dsh-llm-billing": "^0.3.13"
+    "@rayadesu/dsh-client-ui-billing": "^0.3.14",
+    "@rayadesu/dsh-llm-billing": "^0.3.14"
   },
   "devDependencies": {
     "@deepseek-ai/cordis": "^4.0.2",