@blackbelt-technology/pi-agent-dashboard 0.2.1 → 0.2.3

package/AGENTS.md

@@ -56,7 +56,7 @@ make clean              # Destroy all cloned VMs
 | File | Purpose |
 |------|---------|
 | `src/shared/protocol.ts` | Extension↔Server WebSocket messages |
-| `src/shared/browser-protocol.ts` | Server↔Browser WebSocket messages |
+| `src/shared/browser-protocol.ts` | Server↔Browser WebSocket messages (all message types including PromptBus `prompt_request`/`prompt_dismiss`/`prompt_cancel` must be in the `ServerToBrowserMessage` union — `as any` switch cases are stripped by esbuild in production) |
 | `src/shared/types.ts` | Data models (Session, Workspace, Event) |
 | `src/shared/config.ts` | Shared config loader (`~/.pi/dashboard/config.json`) |
 | `src/extension/bridge.ts` | Main extension entry point (composes sync/tracker/flow modules, tracks `isAgentStreaming` in persistent BridgeState) |
@@ -83,7 +83,9 @@ make clean              # Destroy all cloned VMs
 | `src/client/components/BranchPicker.tsx` | Typeahead branch picker with keyboard navigation |
 | `src/client/components/BranchSwitchDialog.tsx` | Checkout orchestration: dirty-state stash, pop prompt |
 | `src/client/lib/git-api.ts` | Client-side fetch helpers for git API endpoints |
-| `src/extension/ui-proxy.ts` | Proxies ctx.ui dialogs to dashboard (confirm/select/input/editor/notify) |
+| `src/extension/prompt-bus.ts` | PromptBus — unified prompt routing to registered adapters (TUI, dashboard, custom). First-response-wins, cross-adapter dismissal. |
+| `src/extension/dashboard-default-adapter.ts` | Built-in PromptBus adapter that renders prompts as generic interactive dialogs in dashboard chat |
+| `src/client/lib/prompt-component-registry.ts` | Client-side component registry mapping prompt type strings to render metadata (placement, component) |
 | `src/extension/ask-user-tool.ts` | `ask_user` tool registration (bundled in bridge, registered at session_start to avoid static tool-name conflicts with other extensions) |
 | `src/shared/openspec-activity-detector.ts` | Detects OpenSpec activity from tool events; auto-attach requires only changeName (phase optional) |
 | `src/shared/openspec-poller.ts` | OpenSpec CLI polling (shared, used by server DirectoryService) |
@@ -155,7 +157,11 @@ make clean              # Destroy all cloned VMs
 | `src/client/hooks/useAuthStatus.ts` | Client auth status hook and login redirect helper |
 | `src/server/localhost-guard.ts` | Network access guard: `createNetworkGuard` (loopback/trusted/authenticated), `isBypassedHost` (CIDR/wildcard/exact), netmask-to-CIDR helpers |
 | `src/server/server-pid.ts` | PID file management for daemon mode |
-| `src/client/components/ServerSelector.tsx` | Server selector dropdown for switching between discovered dashboard servers |
+| `src/client/components/ServerSelector.tsx` | Server selector dropdown showing persisted known servers with availability probing |
+| `src/client/components/KnownServersSection.tsx` | Settings section: list/add/remove persisted known remote servers |
+| `src/client/components/NetworkDiscoverySection.tsx` | Settings section: mDNS network scan with "Add" action and label prompt |
+| `src/client/lib/known-servers-api.ts` | Client-side fetch helpers for known servers CRUD and discovery endpoints |
+| `src/server/routes/known-servers-routes.ts` | REST routes: known servers CRUD, on-demand mDNS discovery scan |
 | `src/server/terminal-manager.ts` | PTY lifecycle, ring buffer, spawn/attach/kill terminals |
 | `src/server/terminal-gateway.ts` | Binary WebSocket upgrade handler for `/ws/terminal/:id` |
 | `scripts/fix-pty-permissions.cjs` | Postinstall: fix node-pty spawn-helper execute permissions |
@@ -200,8 +206,8 @@ make clean              # Destroy all cloned VMs
 | `src/client/hooks/useZoomPan.ts` | Reusable zoom/pan hook (wheel, drag, pinch, buttons) |
 | `src/client/hooks/useMessageHandler.ts` | WebSocket message dispatch hook (extracted from App.tsx) |
 | `src/client/hooks/useSessionActions.ts` | Session action callbacks hook (send, abort, resume, spawn, etc.) |
-| `src/client/hooks/useOpenSpecActions.ts` | OpenSpec action callbacks hook (refresh, archive, attach, detach) |
-| `src/client/hooks/useContentViews.ts` | Content view state + fetch (pi resources, readme, file preview) |
+| `src/client/hooks/useOpenSpecActions.ts` | OpenSpec action callbacks hook (refresh, archive, attach, detach); calls `clearAllContentViews` before opening preview |
+| `src/client/hooks/useContentViews.ts` | Content view state + fetch (pi resources, readme, file preview); `clearAll()` resets all hook-owned states; `onBeforeOpen` callback for cross-component clearing |
 | `src/client/lib/event-reducer.ts` | Event-sourced state reducer (delegates flow events to flow-reducer); extracts LLM errors from `agent_end` into `lastError` |
 | `src/client/hooks/usePendingPromptTimeout.ts` | 30-second safety timeout for stuck `pendingPrompt` spinners |
 | `src/client/lib/flow-reducer.ts` | Flow state machine: all flow_* event handling |
@@ -260,7 +266,7 @@ make clean              # Destroy all cloned VMs
 | `packages/electron/scripts/test-electron-install.sh` | Full e2e Docker test: install, wizard, server launch, health check |
 | `packages/electron/scripts/test-electron-install-inner.sh` | Inner test script run inside Docker container |
 | `packages/electron/resources/icon.png` | Master 1024×1024 app icon (π on dark navy) |
-| `.github/workflows/electron-build.yml` | CI: builds DMG (macOS), DEB+AppImage (Linux), NSIS (Windows) on native runners |
+| `.github/workflows/publish.yml` | CI: builds DMG (macOS), DEB+AppImage (Linux), NSIS+ZIP+portable (Windows) on native runners; publishes npm + GitHub Release |
 
 ## Build & Restart Workflow
 

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Robert Csakany
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -428,7 +428,7 @@ curl -X POST http://localhost:8000/api/restart -H 'Content-Type: application/jso
 src/
 ├── shared/           # Shared TypeScript types
 │   ├── protocol.ts        # Extension ↔ Server messages
-│   ├── browser-protocol.ts # Server ↔ Browser messages
+│   ├── browser-protocol.ts # Server ↔ Browser messages (incl. PromptBus types)
 │   ├── types.ts           # Data models
 │   ├── config.ts          # Shared config loader
 │   └── rest-api.ts        # REST API types
@@ -534,7 +534,7 @@ Output by platform:
 |----------|--------|----------|
 | macOS | `.dmg` | `packages/electron/out/make/` |
 | Linux | `.deb` + `.AppImage` | `packages/electron/out/make/` |
-| Windows | `.exe` (NSIS installer) | `packages/electron/out/make/` |
+| Windows | `.exe` (NSIS installer) + `.zip` + portable `.exe` | `packages/electron/out/make/` |
 
 ### Cross-Platform Builds (via Docker)
 

package/docs/architecture.md

@@ -31,12 +31,13 @@ A global pi extension that runs in every pi session. It:
 - Detects OpenSpec activity (phase/change) from tool events; server auto-attaches the change when `changeName` is detected (phase is not required — skills loaded via prompt templates don't emit a SKILL.md read event). The session card's OpenSpec activity badge displays when either `openspecPhase` or `openspecChange` is detected (not just phase).
 - **Duplicate bridge prevention**: Uses `process`-level shared state (not `globalThis`) with a monotonic generation counter. When the extension is loaded multiple times (e.g., local + global npm package), only the latest instance's event handlers are active — stale listeners bail out immediately. All previous connections and timers are tracked and cleaned up on re-init.
 - **Subagent re-entry guard**: When pi-subagents launches an Agent tool, the subagent creates its own `AgentSession` which loads extensions (including the bridge) in the same process. Without protection, this would overwrite the parent bridge's global state, disconnect its WebSocket, and prevent `tool_execution_end`/`agent_end` from being forwarded — leaving the parent session stuck at "streaming" forever. The bridge stores a reference to its owning `pi` instance and skips initialization when called from a different instance (subagent).
-- Proxies `ctx.ui` dialog methods (confirm, select, input, editor) to the dashboard via `ui-proxy.ts`
-  - TUI sessions: races terminal dialog against dashboard response (first wins)
-  - Race cancellation: when dashboard wins, TUI dialog is aborted via `AbortSignal`; when TUI wins, dashboard dialog is dismissed via `extension_ui_dismiss` message
-  - Headless sessions: only dashboard can respond
-  - Fire-and-forget methods (notify) are forwarded alongside the original call
-  - Re-sends pending UI requests on WebSocket reconnect (server restart resilience)
+- Routes `ctx.ui` dialog methods (confirm, select, input, editor, notify) through `PromptBus` (`prompt-bus.ts`)
+  - Adapters register to handle prompts: `DashboardDefaultAdapter` renders generic dialogs inline; extensions (e.g. pi-flows) can register custom adapters via `prompt:register-adapter` event
+  - First-response-wins: multiple adapters (TUI, dashboard, custom) can claim a prompt; the first to respond resolves it, others are dismissed
+  - Bridge's TUI adapter is registered inline (captures original `ctx.ui` methods before patching) and presents prompts in the terminal with AbortController-based cancellation
+  - Patched `ctx.ui` methods forward the `message` field (from opts) via `metadata` in the PromptBus request
+  - Client-side `prompt-component-registry.ts` maps component type strings to render placement (inline, widget-bar, overlay)
+  - Protocol messages: `prompt_request`, `prompt_dismiss`, `prompt_cancel`, `prompt_response`
 
 ### 2. Dashboard Server (`src/server/`)
 A Node.js HTTP + WebSocket server that:
@@ -78,7 +79,7 @@ A React-based responsive web UI that:
 ### 4. Shared Types (`src/shared/`)
 TypeScript type definitions shared across all components:
 - `protocol.ts` - Extension↔Server WebSocket messages
-- `browser-protocol.ts` - Server↔Browser WebSocket messages
+- `browser-protocol.ts` - Server↔Browser WebSocket messages (includes PromptBus messages: `prompt_request`, `prompt_dismiss`, `prompt_cancel`)
 - `types.ts` - Data models (Session, Workspace, Event, etc.)
 
 ## Data Flow
@@ -90,25 +91,38 @@ TypeScript type definitions shared across all components:
 4. Server broadcasts to all subscribed browsers via `event` message
 5. Browser's event reducer processes event, React renders update
 
-### Interactive UI Flow (extension dialog → browser → response)
+### Interactive UI Flow (PromptBus — extension dialog → browser → response)
 1. Extension calls `ctx.ui.confirm()` / `select()` / `input()` / `editor()`
-2. Bridge UI proxy intercepts, sends `extension_ui_request` to server
-3. Server tracks the request in `pendingUiRequests` map and forwards to subscribed browsers
-4. Browser renders interactive card inline in chat (renderers in `interactive-renderers/`)
-5. User clicks Allow/Deny/option/submits text
-6. Browser sends `extension_ui_response` to server, optimistically clears "Waiting for input" on session card
-7. Server clears the request from `pendingUiRequests` and routes response to bridge extension
-8. Bridge UI proxy resolves the original dialog promise
-
-**Race cancellation (TUI sessions):**
-- TUI and dashboard both show the dialog simultaneously via `Promise.race`
-- When dashboard answers first: TUI dialog is dismissed via `AbortSignal` (passed in `ExtensionUIDialogOptions.signal`)
-- When TUI answers first: bridge sends `extension_ui_dismiss` to server → forwarded as `ui_dismiss` to browsers → dashboard transitions dialog to "dismissed" ("Answered in terminal")
-- Pending Map entry is cleaned up immediately when TUI wins, preventing memory leaks
+2. Bridge PromptBus intercepts via patched `ctx.ui` methods, creates a `PromptRequest` with a unique `promptId` and `pipeline` tag (e.g. `"command"`, `"architect"`)
+3. Registered adapters claim the prompt:
+   - `DashboardDefaultAdapter` (always registered) returns a `PromptClaim` with `component: { type: "generic-dialog", props }` and `placement: "inline"`
+   - Custom adapters (e.g. `ArchitectUIAdapter` from pi-flows) can claim with custom component types and widget-bar placement
+   - TUI adapters (registered via `prompt:register-adapter` event) can claim to show a terminal dialog
+4. Bus sends `prompt_request` to server with the winning adapter's component info
+5. Server forwards to subscribed browsers
+6. Browser's `prompt-component-registry.ts` resolves the component type to a React renderer and placement
+7. User responds in browser → `prompt_response` sent to server → routed to bridge
+8. Bus resolves the original dialog promise and calls `onResponse()` on all adapters for cleanup
+
+**First-response-wins (multi-adapter):**
+- Multiple adapters can claim the same prompt (e.g. TUI + dashboard)
+- The first adapter to respond wins; the bus sends `prompt_dismiss` to the server for the losing adapter's dashboard component
+- Adapters implement `onCancel()` for cleanup when another adapter wins
+
+**Custom UI components:**
+- Extensions register adapters via `pi.events.emit("prompt:register-adapter", adapter)`
+- Adapters return custom `PromptClaim` with arbitrary component types (e.g. `"architect-prompt"`)
+- Client-side registry maps type strings to render placement; unknown types fall back to `"generic-dialog"`
+
+**Message passthrough:**
+- The `message` field from `ask_user` tool (and other `ctx.ui` callers) is forwarded via `metadata.message` in the PromptBus request, through the `prompt_request` protocol message, and extracted by the client into the interactive renderer's `params.message`.
+
+**Type safety:**
+- `prompt_request`, `prompt_dismiss`, and `prompt_cancel` **must** be in the `ServerToBrowserMessage` union in `browser-protocol.ts`. If they are only handled via `case "..." as any:` in switch statements, esbuild's dead-code elimination will strip the handlers in production builds, silently breaking the interactive UI.
 
 **Resilience:**
-- **Page refresh**: Server replays pending `extension_ui_request` messages when a browser subscribes, so interactive dialogs survive page refreshes.
-- **Server restart**: Bridge UI proxy re-sends all pending requests on WebSocket reconnect (`resendPending()`), so dialogs survive server restarts.
+- **Page refresh**: Server replays pending `prompt_request` messages when a browser subscribes. Client deduplicates by `requestId` or pending title match.
+- **Bridge reconnect**: Bridge replays pending PromptBus requests on WebSocket reconnect so dashboard dialogs survive server restarts.
 
 ### Command Flow (browser → pi)
 1. User types prompt or command in browser
@@ -149,7 +163,7 @@ Inline stop buttons also appear on running tool cards in `ToolCallStep`, providi
 Consecutive tool calls with the same name and identical args (e.g. health check polling loops) are collapsed into a single expandable group showing a count badge (e.g. "×24"). Implemented via `groupConsecutiveToolCalls()` in the chat rendering pipeline. Groups require 3+ calls; running tools are never grouped.
 
 **Fork decisions and subagent ask_user:**
-- Already work through existing UI proxy — `TuiFlowIOAdapter` calls `ctx.ui.select/confirm/input` which the bridge wraps and races between TUI and dashboard
+- Work through PromptBus — `TuiFlowIOAdapter` calls `ctx.ui.select/confirm/input` which the bridge routes through the bus to registered adapters (dashboard, TUI, or custom)
 
 **Flow launcher:**
 - Available flows detected from session commands list (heuristic: `source: "extension"`, excluding management commands)
@@ -279,6 +293,18 @@ The web client includes a generic `MarkdownPreviewView` component that replaces
 ### Archive Browser
 The `ArchiveBrowserView` provides a searchable, date-grouped listing of archived OpenSpec changes. It uses a dedicated `GET /api/openspec-archive?cwd=<path>` endpoint that scans `openspec/changes/archive/` and returns entry metadata (name, date, artifacts). The view uses two-level navigation: the list is the first level, and clicking an artifact letter (P/D/S/T) opens the reader as the second level. Back from the reader returns to the list (preserving search and scroll), and back from the list returns to the session view. Entry point is the `[Archive]` button in `FolderOpenSpecSection`.
 
+### Content View Management
+
+The content area (right panel) shows one view at a time: ChatView, ArchiveBrowserView, SpecsBrowserView, PiResourcesView, MarkdownPreviewView (readme, pi resource file, flow YAML, OpenSpec artifact), FileDiffView, FlowArchitectDetail, or FlowAgentDetail. Each view is controlled by independent state in `App.tsx` and `useContentViews`. A priority chain in the JSX determines which view renders (first truthy state wins).
+
+**Mutual exclusivity**: A `clearAllContentViews()` helper resets all content view states. It is called before opening any new content view, ensuring the previous view is always dismissed. This combines `clearAppContentViews()` (App-level states: preview, specs browser, archive browser, diff view, flow YAML, architect detail, flow agent detail) with `clearContentViews()` from `useContentViews` (pi resources, pi resource file preview, readme preview).
+
+**Session switch**: When the selected session changes, `clearAllContentViews()` is called to dismiss any open content view.
+
+**Sub-navigation**: `handleViewPiResourceFile` (viewing a file within PiResourcesView) does not clear other views — it's sub-navigation within an already-active content view.
+
+**`onBeforeOpen` callback**: `useContentViews` accepts an optional `onBeforeOpen` callback. When `handleOpenPiResources` or `handleViewReadme` opens a new top-level view, it calls `onBeforeOpen` first so App.tsx can clear its own states, then clears the hook's sibling states internally.
+
 ### Network Access Control
 
 The server has a two-layer access model:
@@ -499,12 +525,26 @@ The dashboard uses mDNS (via `bonjour-service`) for zero-config server discovery
 - `isDashboardRunning(port)` replaces `isPortOpen(port)` for identity-verified detection
 - After auto-starting, the bridge waits up to 10s for the server's mDNS advertisement
 
+### Known Servers
+- Users can persist remote servers in `config.json` via `knownServers: KnownServer[]`
+- Each entry has `host`, `port`, optional `label`, and `addedAt` timestamp
+- REST API: `GET/POST/DELETE /api/known-servers` for CRUD, `POST /api/discover-servers` for on-demand mDNS scan
+- Localhost is always implicitly available (not stored)
+- The data model is extensible for future key exchange / auth tokens
+
 ### Server Selector UI
-- A dropdown in the sidebar header shows all discovered servers (local + LAN)
-- Each entry shows hostname, port, Local/Remote badge, and connection status
+- The header dropdown shows persisted known servers (from config) plus localhost, not raw mDNS results
+- Each entry shows label (or hostname), host:port, Local/Remote badge, and availability status
+- Non-current servers are probed via health check when the dropdown opens
 - Switching closes the current WebSocket and connects to the selected server
 - Last-used server persisted in `localStorage` (`pi-dashboard-last-server`)
 
+### Server Management (Settings Panel)
+- **Known Servers section**: lists persisted servers with remove buttons and an inline add form (host, port, label)
+- **Network Discovery section**: "Scan network" triggers `POST /api/discover-servers`, shows results with "Add" button that prompts for a label
+- Already-known servers show "Already added" badge in discovery results
+- Electron loading page shows known servers as fallback when primary server is unreachable
+
 ## Provider Authentication
 
 The dashboard supports browser-based authentication with pi's LLM providers, enabling login from phones, tablets, or remote tunnel access without needing terminal access.
@@ -612,6 +652,19 @@ All code-server traffic is proxied through `/editor/:id/*` on the dashboard serv
 
 Binary auto-detection order: config override → `code-server` on PATH → `openvscode-server` on PATH.
 
+### Known Servers Configuration
+
+```json
+{
+  "knownServers": [
+    { "host": "office-mac.local", "port": 8000, "label": "Office Mac", "addedAt": "2024-01-15T10:30:00Z" },
+    { "host": "build-server", "port": 8000, "addedAt": "2024-01-20T14:00:00Z" }
+  ]
+}
+```
+
+Managed via REST API (`/api/known-servers`) or Settings panel. Localhost is always implicit.
+
 ## Bundled Skill: pi-dashboard
 
 The `.pi/skills/pi-dashboard/` directory is both a local project skill (discovered by pi from `.pi/skills/`) and shipped with the npm package (discovered via `pi.skills` in `package.json`). This means any pi session in the dashboard project or any project that installs the dashboard package gets access to the skill.

package/package.json

@@ -1,11 +1,12 @@
 {
   "name": "@blackbelt-technology/pi-agent-dashboard",
-  "version": "0.2.1",
+  "version": "0.2.3",
   "description": "Web dashboard for monitoring and interacting with pi agent sessions",
   "repository": {
     "type": "git",
     "url": "https://github.com/BlackBeltTechnology/pi-agent-dashboard"
   },
+  "license": "MIT",
   "publishConfig": {
     "access": "public"
   },
@@ -41,7 +42,8 @@
     "packages/dist/",
     "docs/architecture.md",
     "AGENTS.md",
-    "README.md"
+    "README.md",
+    "LICENSE"
   ],
   "scripts": {
     "dev": "npm run dev --workspace=@blackbelt-technology/pi-dashboard-web",

package/packages/extension/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@blackbelt-technology/pi-dashboard-extension",
-  "version": "0.2.1",
+  "version": "0.2.3",
   "description": "Pi bridge extension for pi-dashboard",
   "type": "module",
   "pi": {

package/packages/extension/src/__tests__/ask-user-tool.test.ts

@@ -81,5 +81,55 @@ describe("registerAskUserTool", () => {
       await tool.execute("id", { method: "input", title: "Q" }, undefined, undefined, ctx);
       expect(ctx.ui.input).toHaveBeenCalledWith("Q", undefined, undefined);
     });
+
+    it("falls back to message when title is missing", async () => {
+      const { tool, ctx } = getToolAndMockCtx();
+      await tool.execute("id", { method: "input", message: "Detailed question" }, undefined, undefined, ctx);
+      expect(ctx.ui.input).toHaveBeenCalledWith("Detailed question", undefined, { message: "Detailed question" });
+    });
+
+    it("falls back to 'Question' when both title and message are missing", async () => {
+      const { tool, ctx } = getToolAndMockCtx();
+      await tool.execute("id", { method: "confirm" }, undefined, undefined, ctx);
+      expect(ctx.ui.confirm).toHaveBeenCalledWith("Question", "");
+    });
+
+    it("parses options from JSON string", async () => {
+      const { tool, ctx } = getToolAndMockCtx();
+      await tool.execute("id", { method: "select", title: "Pick", options: '["A", "B"]' }, undefined, undefined, ctx);
+      expect(ctx.ui.select).toHaveBeenCalledWith("Pick", ["A", "B"], undefined);
+    });
+
+    it("handles malformed options string gracefully", async () => {
+      const { tool, ctx } = getToolAndMockCtx();
+      await tool.execute("id", { method: "select", title: "Pick", options: "not json" }, undefined, undefined, ctx);
+      expect(ctx.ui.select).toHaveBeenCalledWith("Pick", [], undefined);
+    });
+  });
+
+  describe("prepareArguments", () => {
+    function getTool() {
+      const pi = createMockPi();
+      registerAskUserTool(pi as any);
+      return pi.registerTool.mock.calls[0][0];
+    }
+
+    it("parses stringified options array", () => {
+      const tool = getTool();
+      const result = tool.prepareArguments({ method: "select", title: "Pick", options: '["A", "B"]' });
+      expect(result.options).toEqual(["A", "B"]);
+    });
+
+    it("leaves real array options unchanged", () => {
+      const tool = getTool();
+      const result = tool.prepareArguments({ method: "select", title: "Pick", options: ["A", "B"] });
+      expect(result.options).toEqual(["A", "B"]);
+    });
+
+    it("leaves malformed string as-is", () => {
+      const tool = getTool();
+      const result = tool.prepareArguments({ method: "select", title: "Pick", options: "not json" });
+      expect(result.options).toBe("not json");
+    });
   });
 });

package/packages/extension/src/__tests__/dashboard-default-adapter.test.ts

@@ -0,0 +1,77 @@
+import { describe, it, expect } from "vitest";
+import { DashboardDefaultAdapter } from "../dashboard-default-adapter.js";
+import type { PromptRequest } from "../prompt-bus.js";
+
+function makePrompt(overrides: Partial<PromptRequest> = {}): PromptRequest {
+  return {
+    id: "test-1",
+    pipeline: "command",
+    type: "select",
+    question: "Pick one:",
+    options: ["A", "B"],
+    ...overrides,
+  };
+}
+
+describe("DashboardDefaultAdapter", () => {
+  it("has name 'dashboard-default'", () => {
+    const adapter = new DashboardDefaultAdapter();
+    expect(adapter.name).toBe("dashboard-default");
+  });
+
+  it("claims all prompts with generic-dialog component", () => {
+    const adapter = new DashboardDefaultAdapter();
+    const claim = adapter.onRequest(makePrompt());
+
+    expect(claim).toEqual({
+      component: {
+        type: "generic-dialog",
+        props: {
+          question: "Pick one:",
+          type: "select",
+          options: ["A", "B"],
+          defaultValue: undefined,
+        },
+      },
+      placement: "inline",
+    });
+  });
+
+  it("claims input prompts with correct props", () => {
+    const adapter = new DashboardDefaultAdapter();
+    const claim = adapter.onRequest(makePrompt({
+      type: "input",
+      question: "Name:",
+      options: undefined,
+      defaultValue: "default",
+    }));
+
+    expect(claim.component!.type).toBe("generic-dialog");
+    expect(claim.component!.props.type).toBe("input");
+    expect(claim.component!.props.defaultValue).toBe("default");
+  });
+
+  it("claims confirm prompts", () => {
+    const adapter = new DashboardDefaultAdapter();
+    const claim = adapter.onRequest(makePrompt({ type: "confirm", question: "Sure?" }));
+
+    expect(claim.component!.type).toBe("generic-dialog");
+    expect(claim.component!.props.type).toBe("confirm");
+  });
+
+  it("placement is always inline", () => {
+    const adapter = new DashboardDefaultAdapter();
+    const claim = adapter.onRequest(makePrompt({ pipeline: "architect-new" }));
+    expect(claim.placement).toBe("inline");
+  });
+
+  it("onResponse does not throw", () => {
+    const adapter = new DashboardDefaultAdapter();
+    expect(() => adapter.onResponse({ id: "x", answer: "A", source: "tui" })).not.toThrow();
+  });
+
+  it("onCancel does not throw", () => {
+    const adapter = new DashboardDefaultAdapter();
+    expect(() => adapter.onCancel("x")).not.toThrow();
+  });
+});

package/packages/extension/src/__tests__/dev-build.test.ts

@@ -42,7 +42,7 @@ describe("runDevBuild", () => {
   it("should log progress messages", () => {
     run();
 
-    const logs = logSpy.mock.calls.map((c) => c[0]);
+    const logs = logSpy.mock.calls.map((c: any) => c[0]);
     expect(logs).toContain("🔨 Dashboard: building client...");
     expect(logs).toContain("✅ Dashboard: client built");
     expect(logs).toContain("🛑 Dashboard: stopping server...");
@@ -54,7 +54,7 @@ describe("runDevBuild", () => {
 
     run();
 
-    const logs = logSpy.mock.calls.map((c) => c[0]);
+    const logs = logSpy.mock.calls.map((c: any) => c[0]);
     expect(logs).toContain("❌ Dashboard: build failed — build error");
     expect(mockFetch).toHaveBeenCalledWith(
       "http://localhost:8000/api/shutdown",

package/packages/extension/src/__tests__/openspec-activity-detector.test.ts

@@ -93,28 +93,28 @@ describe("detectOpenSpecActivity", () => {
       const result = detectOpenSpecActivity("bash", {
         command: 'openspec status --change "session-sync" --json',
       });
-      expect(result).toEqual({ changeName: "session-sync" });
+      expect(result).toEqual({ changeName: "session-sync", isActive: true });
     });
 
     it("detects change name from openspec instructions command", () => {
       const result = detectOpenSpecActivity("bash", {
         command: 'openspec instructions apply --change "my-feature" --json',
       });
-      expect(result).toEqual({ changeName: "my-feature" });
+      expect(result).toEqual({ changeName: "my-feature", isActive: true });
     });
 
     it("detects change name without quotes", () => {
       const result = detectOpenSpecActivity("bash", {
         command: "openspec status --change session-sync --json",
       });
-      expect(result).toEqual({ changeName: "session-sync" });
+      expect(result).toEqual({ changeName: "session-sync", isActive: true });
     });
 
     it("detects change name from openspec archive command", () => {
       const result = detectOpenSpecActivity("bash", {
         command: "openspec archive session-sync",
       });
-      expect(result).toEqual({ changeName: "session-sync" });
+      expect(result).toEqual({ changeName: "session-sync", isActive: true });
     });
 
     it("returns null for non-openspec bash commands", () => {
@@ -128,21 +128,21 @@ describe("detectOpenSpecActivity", () => {
       const result = detectOpenSpecActivity("bash", {
         command: 'openspec new change "add-auth"',
       });
-      expect(result).toEqual({ changeName: "add-auth" });
+      expect(result).toEqual({ changeName: "add-auth", isActive: true });
     });
 
     it("detects change name from openspec new change with unquoted name", () => {
       const result = detectOpenSpecActivity("bash", {
         command: "openspec new change add-auth",
       });
-      expect(result).toEqual({ changeName: "add-auth" });
+      expect(result).toEqual({ changeName: "add-auth", isActive: true });
     });
 
     it("detects change name from openspec new change with cd prefix", () => {
       const result = detectOpenSpecActivity("bash", {
         command: 'cd /Users/dev/project && openspec new change "my-feature"',
       });
-      expect(result).toEqual({ changeName: "my-feature" });
+      expect(result).toEqual({ changeName: "my-feature", isActive: true });
     });
 
     it("returns null for openspec list (no change name)", () => {
@@ -154,18 +154,18 @@ describe("detectOpenSpecActivity", () => {
   });
 
   describe("change name detection from file reads", () => {
-    it("detects change name from openspec change file read", () => {
+    it("detects change name from openspec change file read as passive", () => {
       const result = detectOpenSpecActivity("read", {
         path: "openspec/changes/session-sync/tasks.md",
       });
-      expect(result).toEqual({ changeName: "session-sync" });
+      expect(result).toEqual({ changeName: "session-sync", isActive: false });
     });
 
-    it("detects change name from absolute path", () => {
+    it("detects change name from absolute path as passive", () => {
       const result = detectOpenSpecActivity("read", {
         path: "/Users/dev/project/openspec/changes/my-feature/proposal.md",
       });
-      expect(result).toEqual({ changeName: "my-feature" });
+      expect(result).toEqual({ changeName: "my-feature", isActive: false });
     });
 
     it("returns null for non-openspec file reads", () => {
@@ -177,18 +177,18 @@ describe("detectOpenSpecActivity", () => {
   });
 
   describe("change name detection from file writes", () => {
-    it("detects change name from openspec change file write", () => {
+    it("detects change name from openspec change file write as active", () => {
       const result = detectOpenSpecActivity("write", {
         path: "openspec/changes/session-sync/proposal.md",
       });
-      expect(result).toEqual({ changeName: "session-sync" });
+      expect(result).toEqual({ changeName: "session-sync", isActive: true });
     });
 
-    it("detects change name from absolute path write", () => {
+    it("detects change name from absolute path write as active", () => {
       const result = detectOpenSpecActivity("write", {
         path: "/Users/dev/project/openspec/changes/my-feature/spec.md",
       });
-      expect(result).toEqual({ changeName: "my-feature" });
+      expect(result).toEqual({ changeName: "my-feature", isActive: true });
     });
 
     it("returns null for non-openspec file writes", () => {
@@ -203,15 +203,15 @@ describe("detectOpenSpecActivity", () => {
     it("handles capitalized tool names (backward compatibility)", () => {
       expect(detectOpenSpecActivity("Read", {
         path: "openspec/changes/my-feature/proposal.md",
-      })).toEqual({ changeName: "my-feature" });
+      })).toEqual({ changeName: "my-feature", isActive: false });
 
       expect(detectOpenSpecActivity("Bash", {
         command: 'openspec status --change "add-auth" --json',
-      })).toEqual({ changeName: "add-auth" });
+      })).toEqual({ changeName: "add-auth", isActive: true });
 
       expect(detectOpenSpecActivity("Write", {
         path: "openspec/changes/my-feature/design.md",
-      })).toEqual({ changeName: "my-feature" });
+      })).toEqual({ changeName: "my-feature", isActive: true });
     });
 
     it("returns null for unknown tool names", () => {