herdr-dashr 0.1.0 → 0.1.2

package/README.md

@@ -1,14 +1,18 @@
 # herdr-dashr
 
 A [Herdr](https://github.com/herdrdev/herdr) plugin that opens an
-**agent-built, live Grafana dashboard inside a Herdr pane**, with a coding
-agent underneath to reshape it.
+**agent-built, live Grafana dashboard inside a Herdr pane**, built and
+reshaped by the AI session you are already talking to.
+
+You only talk to your AI session. Paste a CodePipeline link and say
+*"visualize it on a dashboard"*: its herdr-dashr skill opens the dashboard
+pane beside you and builds the dashboard, then keeps changing it as you ask.
 
 - **Real Grafana, in the terminal.** The top pane shows Grafana in kiosk mode
   through [terminal-browser](https://github.com/zenbu-labs/terminal-browser);
   without it, a text status view.
 - **No model in the data path.** Grafana refreshes the data. The agent only
-  changes the dashboard, through an MCP server.
+  changes the dashboard, through the `dashr` tools (a command line, or MCP).
 - **Privacy by construction.** The agent designs from schemas and masked
   samples (`<email#1>`, `<ipv4#2>`); only you see real values.
 - **Disposable.** A pane-owned Grafana container with a read-only root and
@@ -26,23 +30,36 @@ agent underneath to reshape it.
 
 `docs/PRD.md` is the authoritative specification and delivery ledger.
 
-**Status:** v0.1.0, the first public release. All but one PRD requirement verified (the first npm publish comes with this release), most by an end-to-end
+**Status:** v0.1.2, on GitHub and npm, for Linux, macOS and Windows. Windows support and the AI-session flow are new; everything else is verified, most by an end-to-end
 suite that runs a real Herdr, a real Grafana and terminal-browser in CI.
 
 ## Install
 
+Linux, macOS and Windows:
+
 ```bash
 herdr plugin install czinegeroland/herdr-dashr
 ```
 
-The build step installs the prebuilt `dashr` binary for your platform — from
-npm (`herdr-dashr`), whose platform packages were verified against the
-release's SHA-256 before they were packed; failing that from the GitHub
-release, verified the same way; and only as a last resort with `cargo`. No
-Rust toolchain is needed. `DASHR_INSTALL_SOURCE=npm|github|source` forces one. You need
-Docker. terminal-browser (for the real Grafana UI; it refuses to run as root), Claude Code (the chat
-pane) and the AWS CLI (CodePipeline, CloudWatch) are optional — run the
-**Check dashr prerequisites** action to see what is missing.
+The build step runs `npm install herdr-dashr@<version>` in the plugin
+directory, as herdr-remote-channel does: npm installs the one platform
+package whose prebuilt `dashr` matches your machine (verified against the
+release's SHA-256 before it was packed), and every Herdr entry point runs it
+through `node node_modules/herdr-dashr/bin.js`. You need Node.js 18+ and
+Docker; no Rust toolchain. terminal-browser (for the real Grafana UI; it
+refuses to run as root), Claude Code (the chat pane) and the AWS CLI
+(CodePipeline, CloudWatch) are optional — run the **Check dashr
+prerequisites** action to see what is missing.
+
+Another build step installs the **herdr-dashr skill** for Claude Code with
+`npx skills add czinegeroland/herdr-dashr --skill herdr-dashr --agent
+claude-code --global`, as herdr-remote-channel installs its skill. Your AI
+session also needs the `dashr` command: `npm install -g herdr-dashr` (the
+skill runs it for you when `dashr` is missing).
+
+On Windows, Docker Desktop must be running, and the chat pane's shell is
+PowerShell. Without terminal-browser the dashboard pane shows the Grafana URL;
+Ctrl-click it to open Grafana in your browser.
 
 ### The CLI on its own
 
@@ -57,6 +74,21 @@ from GitHub.
 
 ## Use
 
+Ask your AI session, in Herdr:
+
+- *"Visualize this on a dashboard: https://eu-west-1.console.aws.amazon.com/codesuite/codepipeline/pipelines/api/view"*
+- *"Show me error rates and latency for checkout."*
+- *"I'm about to run the importer — show me its logs and check that `import done` is logged."*
+
+The skill opens the dashboard pane beside the conversation (`herdr plugin
+pane open --plugin herdr-dashr --entrypoint dashboard`), waits for Grafana
+(`dashr wait`) and builds with `dashr tool <name>`: the same tools, masking
+and privacy rules as the MCP server. You never have to leave the
+conversation.
+
+The Herdr actions still work without an AI session of your own; they open a
+tab with Grafana on top and a new agent underneath:
+
 | Action | What it does |
 |---|---|
 | **Open live dashboard** | New tab: Grafana on top, the agent underneath. |
@@ -128,8 +160,11 @@ supported datasource (Prometheus, Loki, Tempo, CloudWatch, SQL Server, Azure
 Monitor, Zabbix, Seq, TestData) and debugging recipes (deploys, queue
 backlogs, Step Functions failures, error spikes, latency).
 
-- Installed by the plugin's build step, refreshed by the dashboard pane when
-  the binary is newer. A skill of the same name that you wrote is never
+- Installed by the plugin's build step with `npx skills add` from this
+  repository, as herdr-remote-channel does. It teaches your own AI session
+  to open the dashboard pane and drive it with `dashr wait` and `dashr tool`.
+- `dashr skill install --dir <skills-dir>` installs the copy embedded in the
+  binary, for other agents; a skill of the same name that you wrote is never
   replaced (`--force` to override).
 - Also served as MCP resources (`dashr://guide/...`), so any MCP agent gets it.
 - `dashr skill files`, `dashr skill print reference/recipes.md`,

package/bin.js

@@ -16,16 +16,18 @@ import { fileURLToPath } from 'node:url'
 import { dirname, join, sep } from 'node:path'
 
 const require = createRequire(import.meta.url)
-const binary = 'dashr'
+const binary = process.platform === 'win32' ? 'dashr.exe' : 'dashr'
 
-// Keep in step with `scripts/build-npm-packages.mjs`, `scripts/install.sh`
-// and the release matrix; `crates/dashr-cli/tests/distribution.rs` holds them
-// together.
+// The package holding each platform's executable. Keep in step with
+// `scripts/build-npm-packages.mjs` (Windows is scoped there, see why),
+// `scripts/install.sh` and the release matrix;
+// `crates/dashr-cli/tests/distribution.rs` holds them together.
 const PACKAGES = {
-  'linux x64': 'linux-x64',
-  'linux arm64': 'linux-arm64',
-  'darwin x64': 'darwin-x64',
-  'darwin arm64': 'darwin-arm64',
+  'linux x64': 'herdr-dashr-linux-x64',
+  'linux arm64': 'herdr-dashr-linux-arm64',
+  'darwin x64': 'herdr-dashr-darwin-x64',
+  'darwin arm64': 'herdr-dashr-darwin-arm64',
+  'win32 x64': '@czinegeroland/herdr-dashr-win32-x64',
 }
 
 // Run from `npm/dashr` inside a source checkout (a symlinked
@@ -51,8 +53,8 @@ if (here.endsWith(`${sep}npm${sep}dashr`)) {
 // The prebuilt executable npm installed for this platform.
 function published() {
   const key = `${process.platform} ${process.arch}`
-  const suffix = PACKAGES[key]
-  if (!suffix) {
+  const pkg = PACKAGES[key]
+  if (!pkg) {
     console.error(
       `dashr: no prebuilt binary for ${key}.\n` +
         `Supported: ${Object.keys(PACKAGES).join(', ')}.\n` +
@@ -60,7 +62,6 @@ function published() {
     )
     process.exit(1)
   }
-  const pkg = `herdr-dashr-${suffix}`
   try {
     return require.resolve(`${pkg}/${binary}`)
   } catch {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "herdr-dashr",
-  "version": "0.1.0",
+  "version": "0.1.2",
   "description": "Agent-built, live Grafana dashboards in a Herdr pane, with masking between your data and the agent.",
   "license": "Apache-2.0",
   "repository": {
@@ -26,10 +26,11 @@
     "README.md"
   ],
   "optionalDependencies": {
-    "herdr-dashr-linux-x64": "0.1.0",
-    "herdr-dashr-linux-arm64": "0.1.0",
-    "herdr-dashr-darwin-x64": "0.1.0",
-    "herdr-dashr-darwin-arm64": "0.1.0"
+    "herdr-dashr-linux-x64": "0.1.2",
+    "herdr-dashr-linux-arm64": "0.1.2",
+    "herdr-dashr-darwin-x64": "0.1.2",
+    "herdr-dashr-darwin-arm64": "0.1.2",
+    "@czinegeroland/herdr-dashr-win32-x64": "0.1.2"
   },
   "engines": {
     "node": ">=18"