What changed
Distribution
-
Published to the npm registry as a scoped package:
@y2zyyr/dsh-token-usage-sidebar(1.1.1onlatest). -
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.