@sixzjd/dsh-usage-dashboard 0.6.0 → 0.6.1

package/CHANGELOG.md

@@ -1,5 +1,20 @@
 # Changelog
 
+## 0.6.1
+
+### Fixed — the settings entry never appeared
+
+The client bundle registered itself as `dsh-usage-dashboard`, but the host keys
+its boot graph by PACKAGE name and asserts that a loaded bundle registered that
+exact id. The bundle loaded and then failed that assertion, so the settings
+section was never mounted — the host half worked (its routes answered) while
+nothing showed in the UI.
+
+Escaped 0.6.0 because the rename changed the package name to
+`@sixzjd/dsh-usage-dashboard` without changing the bundle id inside
+`client.js`. Every other working client plugin in the profile registers under
+its full package name; this one now does too, and a test pins the two together.
+
 ## 0.6.0
 
 ### Fixed — deleted sessions no longer erase their usage

package/client.js

@@ -1,5 +1,10 @@
+// The bundle id MUST be the package name: the host composes its boot graph
+// keyed by package (`client-modules` passes the Loader row's package name as
+// the resource id) and the browser asserts that a loaded bundle registered
+// exactly that id. A bare plugin id here makes the bundle load but never
+// satisfy the manifest, so the settings entry silently never appears.
 window.__ModuleLoader__.load({
-  id: "dsh-usage-dashboard",
+  id: "@sixzjd/dsh-usage-dashboard",
   factory: (require) => {
     const React = require("react");
     const SUMMARY_PATH = "/api/dsh-usage-dashboard/summary";

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@sixzjd/dsh-usage-dashboard",
   "displayName": "用量统计",
-  "version": "0.6.0",
+  "version": "0.6.1",
   "description": "Usage statistics for DeepSeek Harness: daily token usage, request count, cache hit rate and estimated cost as a native settings section, with durable history that survives deleted sessions.",
   "type": "module",
   "main": "lib/index.js",