dsh-all-usage v1.1.3

Highlights / 主要更新

• Added validated context-tiered official pricing, expandable rate schedules, and explicit price overrides.
• Reworked the durable usage ledger with stable shards, dirty-flush coalescing, revision reuse, and safe incremental/full recovery.
• Built scoped queries, trends, and the fixed 53-week heatmap from ingest-time aggregates to reduce cold historical scans.
• Hardened deterministic pricing catalogs, pricing sync, official-model search, mapping refresh races, and recovery for invalid sequences or lagging persistence revisions.
• Added Node 22/24, DSH rc.1/rc.2 runtime smoke, fixture replay, syntax, and package-content release gates.

Validation / 验证

• Node 22 and Node 24: 170 tests passed.
• Real Cordis runtime smoke passed on DSH 0.1.1-rc.1 and 0.1.1-rc.2.
• Fixture replay, syntax checks, package checks, and the GitHub CI workflow passed.
• Release artifact: dsh-all-usage-1.1.3.tgz (22 files, SHA-256 0e3270dc95d106c8fc6221715bda69cbc0c13a7f044c7dca1358ea4e10d00fb).

See CHANGELOG.md for the complete release record.

dsh-all-usage v1.1.2

模型与工作区圆环及列表新增 Token、成本和占比展示；Host 增加日期索引、快照/日志缓存、实时事件恢复与写入生命周期保护；成本设置模型检索加入防抖；更新插件自有截图。

dsh-all-usage v1.1.1

dsh-all-usage v1.1.1

• Reissued the v1.1 dashboard package under a new patch version for npm registry compatibility.
• Includes the full v1.1 dashboard feature set, performance optimizations, and seven screenshot assets.
• The existing v1.1.0 Release remains available as historical output.

dsh-all-usage v1.1.0

dsh-all-usage v1.1.0

• 完成结构化模型身份与 ledger v2 兼容升级
• 增加 scoped query/records API 与隐私安全分页日志
• 今日趋势按小时，跨日趋势按日
• 增加模型与工作区 Token 占比环图
• 优化筛选、日志、热力图和 Client/Host 性能
• 纳入七张 dashboard 截图资产

dsh-all-usage v1.0.9

dsh-all-usage v1.0.9

Added

• Data health: the dashboard now reports historical scan completion, persistence snapshot availability, revision-skipped sessions, actual log reads, ledger-only recovery, and scan failures.
• Lightweight status contract: GET /api/all-usage/status exposes only the Host instance, monotonic stats revision, scan state, and non-sensitive sync counters. It never exposes session IDs, workspace paths, prompts, replies, totals, or the write capability token.
• On-demand refresh: after historical scanning completes, the client polls lightweight status and downloads the full usage snapshot only when the Host instance or stats revision changes.

Fixed

• Failed status or full-snapshot requests now preserve the last successful dashboard data, show it as stale, expose retry, and use bounded retry backoff.
• The sidebar dashboard now passes the injected timer service into its view, so the usage dialog mounts correctly after opening.
• Refreshed the plugin-owned dashboard screenshots.

Verification

• npm test: 38/38 pass.
• Host and Client syntax checks, npm pack --dry-run --json, and git diff --check pass.
• Verified against the active DSH Host: the status endpoint is lightweight and guarded, and real restart scan health reported revision reuse, log reads, ledger recovery, and zero failures.

dsh-all-usage v1.0.8

dsh-all-usage v1.0.8

Added

• Restart read-avoidance: on startup the plugin now uses the persisted log revision (via sessionPersistence.listSnapshots() — a header-line + stat read, no full-log parse) as a per-session change signal. Sessions whose log is unchanged since the last ledger write are applied straight from the durable ledger without reading their full event log; only changed or new sessions are read (incrementally).
• The durable ledger now stores each session's log revision (lastRevision); existing rows without it are re-read once and backfilled, so the upgrade is backward compatible.

Fixed

• Eliminated the per-session full-event read at restart for unchanged persisted sessions — DSH restarts no longer re-read every session's history from scratch.

Verification

• npm test 31/31 (incl. restart-skip with zero reads, revision-change re-read, and old-row backfill tests).
• node --check Host + Client, npm pack --dry-run, git diff --check all pass; hot-reload and a real DSH restart both verified.

dsh-all-usage v1.0.7

dsh-all-usage v1.0.7

Added

• Incremental scan cursor: baseline rescans reuse the durable usage ledger as a per-session cursor. Unchanged sessions seed straight from the ledger instead of re-folding every historical event; sessions that gained events fold only the new tail.
• All-zero usage guard: zero-usage replays no longer overwrite already-recorded turn/step usage, while pure cache-read requests (cache-only hits) still count.
• Structured token semantics: /api/all-usage now declares a machine-readable accounting contract (tokenSemantics.semantics) — input tokens are fresh (exclude cache), and cache read/write plus reasoning are separate buckets.

Fixed

• Reduced startup scan cost on long usage history: unchanged sessions are no longer re-folded or rewritten.
• Prevented a live retry of an already-recorded step from double-counting after a fresh-instance ledger seed.

Verification

• npm test 28/28 (incl. new aggregation tests: incremental seed, zero-usage guard, cache-only retention, semantics contract).
• node --check Host + Client, npm pack --dry-run, git diff --check all pass.

v1.0.6

Fixed

• Preserve successfully flushed usage in a durable per-session ledger after conversation logs are deleted
• Rehydrate deleted-session usage across plugin reloads and rebuilds without double-counting
• Protect baseline scans and ledger writes from stale generations and disposal races
• Handle inactive Cordis timer contexts without fatal DSH load failures
• Use valid storage unit names for the JSON backend

Validation

• 22 automated tests passed
• Host and client syntax checks passed

v1.0.5

Added

• Full historical daily aggregation: custom date ranges now cover every day recoverable from persisted session logs (heatmap stays at the latest 53 weeks)
• Distinct session counts for bounded and custom ranges, including CSV export

Fixed

• Baseline scan retries with backoff after a transient registry failure instead of reporting an empty completed scan
• In-flight scans stop after plugin disposal or hot reload
• Stale stats/balance responses can no longer overwrite newer ones

Validation

• 14 automated tests passed

dsh-all-usage v1.0.4

English mode now uses UTC consistently for date buckets, range filters, streaks, heatmap dates, hover labels, CSV filenames, and export timestamps. Chinese mode keeps local time. Adds parallel UTC day aggregation and regression coverage.