dsh-token-usage-sidebar v1.1.1

What changed

Distribution

• Published to the npm registry as a scoped package: @y2zyyr/dsh-token-usage-sidebar (1.1.1 on latest).

• Install / update / remove via the normal DSH plugin surface:

  dsh plugin --profile web add @y2zyyr/dsh-token-usage-sidebar
  dsh plugin --profile web update @y2zyyr/dsh-token-usage-sidebar
  dsh plugin --profile web remove @y2zyyr/dsh-token-usage-sidebar

• GitHub remains the source of code, README, issues, Git tags, and Releases; a direct
  GitHub install (dsh plugin --profile web add github:y2zyyr/dsh-token-usage-sidebar) keeps working.

DSH install / update compatibility (verified on DSH 0.1.0-rc.6, Node 26)

• The npm rename is identity-safe: the Cordis loader entry ID (token-usage-sidebar), the
  exported plugin name, the client module ID, the settings namespace, and the persistent
  SQLite ledger path (<DSH_HOME>/storages/dsh_token_usage_sidebar.sqlite) are all
  package-name independent and unchanged.
• Upgrading an existing v1.1.0 (GitHub) install preserves the full ledger: remove the old
  package name and add the scoped one — no data migration required.

Packaging

• publishConfig.access: public; the tarball was audited before publish and contains only
  runtime files (lib/, client.js, cordis.patch.yml, README*, LICENSE, package.json).
• No runtime code or storage semantics changed in this release.

Local workflow

• A local AGENTS.md (agent project context) is maintained on the owner machine only; it is
  git-ignored, never pushed to GitHub, and not included in the npm package.

dsh-token-usage-sidebar v1.1.0

Major improvement — v1.1 introduces a scalable SQLite-backed durable Token ledger designed for long-running DSH installations.

Upgrade — Existing v1.0.1 usage data is automatically backed up, migrated, and verified before cutover.

Performance — Token writes no longer require copying/re-writing the entire lifetime history.

Reliability — Authoritative invocation records are now the source of truth; aggregates are rebuildable.

Existing UX — Today / Yesterday / Total and Settings analytics remain available.

Privacy — Usage accounting remains local and does not store conversation contents.

Compatibility — Requires a Node.js runtime that exposes the built-in node:sqlite module (CI verifies Node 22 and 24).

dsh-token-usage-sidebar v1.0.1

dsh-token-usage-sidebar v1.0.1

A stable release hardening token-usage accounting, history reporting, and storage safety.

Fixed

• Fixed a shutdown race that could lose very recent token usage before persistence (flush-before-close).
• Hardened historical recovery status so incomplete scans are no longer overstated as complete.
• Added ledger consistency self-healing for stale derived historical counters.
• Added corrupt-store detection to prevent silent zero-reset behavior.
• Hardened sidebar fallback mounting.
• Added expanded regression coverage and GitHub Actions CI.

Features (unchanged from v1.0.0)

• Sidebar summary: Today / Yesterday / Total.
• Native Settings → Token Usage page.
• Honest historical recovery reporting and local persistence.

Notes

• Install: dsh plugin --profile web add github:y2zyyr/dsh-token-usage-sidebar
• Update: dsh plugin --profile web update dsh-token-usage-sidebar
• Removal: dsh plugin --profile web remove dsh-token-usage-sidebar

v1.0.0 Token Usage Insights

Token Usage Insights

v1.0.0 turns the sidebar summary into a complete native Settings → Token Usage experience.

• Four overview cards: All time, Today, Yesterday, and Last 7 days.
• Today / Yesterday / 7D / All time detail ranges with Input, Output, Cache Read, Cache Write, Reasoning, and call counts.
• Provider and model aggregation, sorted by total usage, plus a zero-filled seven-local-day table.
• Aggregate-only local details API; individual ledger records never reach the browser.

Migration

The durable ledger is upgraded to schema v4. On first v1.0.0 launch it replays recoverable session events once to enrich existing calls with exact token buckets and provider/model metadata. Existing IDs are enriched or replaced by a higher-sequence final message, never added to lifetime totals again. Old values that cannot be recovered remain explicitly unclassified rather than being assigned a fabricated date or model.

Validation

• 28 automated accounting, migration, and range-aggregation tests pass.
• Production bundles are rebuilt; client.js and lib/client.js are byte-identical.
• Verified in DeepSeek Harness web profile at 127.0.0.1:3080: settings navigation, all cards, range switching, model table, daily table, and restart-safe totals.

Upgrade

dsh plugin --profile web update dsh-token-usage-sidebar
# Restart dsh web after updating.

No npm publication is required. Existing local accounting is retained.

v0.2.1

Persistent token accounting in the DeepSeek Harness sidebar.

• Today, Yesterday, and lifetime Total
• Historical usage recovery and restart persistence
• Exactly-once, replay-safe accounting
• DeepSeek Harness web sidebar integration