@dipertq/dsh-openviking-status 0.1.5 → 0.1.8

package/README.md

@@ -4,13 +4,29 @@
 
 ## Overview
 
-This DSH UI plugin injects a live status chip into the composer bottom bar (`conversation.input.right`). It provides at-a-glance transparency into OpenViking memory management:
+This DSH UI plugin adds a chip to the composer stats row
+(`conversation.composer.dock`), alongside `24 turns 645 steps`. It provides
+at-a-glance transparency into OpenViking memory management:
 
 - **Server Health**: Online / Offline indicator with live health checks.
 - **Pending Tokens**: Real-time counter of session tokens accumulated before the auto-commit threshold (20,000 tokens).
-- **Peer Scope**: Active project/repository context peer ID.
+- **Recalled Memories**: Count and list of the `viking://` files injected into the current conversation.
 - **Commit Trigger**: Instant "Commit To Memory Now" action button.
 
+## API key
+
+If the daemon runs with `auth_mode: api_key` — check with
+`curl -s http://127.0.0.1:1933/health` — session counters are unreadable
+without a key, and the chip says `no access` rather than showing zeros. The
+browser cannot read `~/.openviking/ovcli.conf`, so supply the key once from the
+DSH devtools console:
+
+```js
+localStorage.setItem("openviking_api_key", "<your key>");
+```
+
+The key from `ovcli.conf` works. Daemons without authentication need nothing.
+
 ## Architecture & Design
 
 See [CONTEXT.md](./CONTEXT.md), [ADR 0001](./docs/adr/0001-client-ui-widget.md), and [ADR 0002](./docs/adr/0002-release-workflow.md).
@@ -33,7 +49,7 @@ Equivalent, and useful when the registry is unreachable. Use a
 **version-pinned** URL:
 
 ```bash
-dsh plugin add https://github.com/dipertq/dsh-openviking-status/releases/download/v0.1.5/dipertq-dsh-openviking-status-0.1.5.tgz
+dsh plugin add https://github.com/dipertq/dsh-openviking-status/releases/download/v0.1.8/dipertq-dsh-openviking-status-0.1.8.tgz
 ```
 
 Not `/releases/latest/download/…`: that URL keeps its name while its content
@@ -98,14 +114,12 @@ authenticates over OIDC with short-lived credentials, so there is no `NPM_TOKEN`
 secret to store or rotate, and each release carries a provenance attestation
 proving which commit and workflow built it.
 
-One-time setup, after the first version exists in the registry (trusted
-publishing is configured per package):
-
-1. Publish `0.1.5` once by hand: `npm publish --access public`.
-2. On the package's **Settings → Trusted Publisher** page, add a GitHub Actions
-   publisher: user `dipertq`, repository `dsh-openviking-status`, workflow
-   `release.yml`, environment blank.
-3. Cut releases as usual — the workflow publishes on its own.
+This is already configured, so a release needs nothing beyond the usual
+`pnpm run release:*`. The one-time setup was: publish the first version by hand
+(trusted publishing is configured per package, so the package has to exist),
+then register a GitHub Actions publisher on the package's
+**Settings → Trusted Publisher** page — user `dipertq`, repository
+`dsh-openviking-status`, workflow `release.yml`, environment blank.
 
 ## License