@huseynsnmz/pi-board 0.0.0-stage → 0.14.0

package/README.md

@@ -1,3 +1,440 @@
-# Temporary Holding Version
+# pi-board
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+<p align="center">
+  <img src="https://raw.githubusercontent.com/huseynsnmz/pi-board/main/assets/banner.png" alt="Pi Agent Board" width="100%" />
+</p>
+
+<p align="center">
+  <a href="https://github.com/huseynsnmz/pi-board/blob/main/assets/demo.mp4"><strong>30s demo</strong></a>
+  | <a href="https://pi.dev/packages?name=@huseynsnmz/pi-board">Pi package gallery</a>
+  | <a href="https://www.npmjs.com/package/@huseynsnmz/pi-board">npm</a>
+</p>
+
+pi-board is a full-screen TUI dashboard for [Pi](https://github.com/earendil-works/pi-mono) that manages durable background Pi sessions. Use one global board to dispatch work across projects, watch progress, triage summaries and evidence, reply without opening a transcript, and attach to a real interactive session when hands-on work is needed.
+
+It started as a fork of [`@zhuxixi/pi-agent-board`](https://github.com/zhuxixi/pi-agent-board) 0.13.1, so the design and most of the code are theirs, under the MIT license. The command is still `/agent-board`.
+
+## What It Does
+
+- Run several Pi tasks at once without losing track of their current state.
+- Keep each task as a real, resumable Pi session that survives `/reload`, closing Pi, or restarting the terminal.
+- Triage the latest output, blockers, evidence, and diagnostics before opening a full transcript.
+- Reply to a session without attaching; replies sent while a session is busy are preserved for later delivery.
+- Fall back to a JSON runner for eligible background work when live PTY support is unavailable.
+
+> **Write-safety note:** Worktree isolation is currently disabled. Multiple sessions in the same repository may run concurrently, so avoid overlapping writes or provide your own isolation.
+
+## Requirements
+
+- [Pi](https://github.com/earendil-works/pi-mono) installed and working.
+- Node.js 20 or newer.
+- Working Pi provider authentication for real model execution. Agent Board does not have a separate login or credential store.
+- PTY support from `node-pty` for live attach and **start & attach**. Background work can use a JSON-runner fallback when PTY support is unavailable.
+
+If rows remain in `Running`, first verify that Pi itself can complete a one-shot model call:
+
+```bash
+pi --mode json -p --no-session "Reply with exactly: DONE"
+```
+
+A healthy command emits an assistant `message_end`, then an `agent_end` event, and exits. See [VERIFY.md](VERIFY.md) for the complete no-auth, provider-auth, and PTY checks.
+
+## Install
+
+### Published package
+
+```bash
+pi install npm:@huseynsnmz/pi-board
+```
+
+Start Pi normally and run `/agent-board`, or use one of the startup entry points below.
+
+### Local checkout
+
+```bash
+npm install
+pi install "$(pwd)"
+```
+
+This installs the current checkout as a Pi package. Remove that path installation with:
+
+```bash
+pi remove "$(pwd)"
+```
+
+### Development auto-discovery
+
+To have Pi load the checkout directly while developing:
+
+```bash
+ln -s "$(pwd)" ~/.pi/agent/extensions/agent-board
+pi
+```
+
+Remove the symlink when you no longer want Pi to auto-load the checkout:
+
+```bash
+rm ~/.pi/agent/extensions/agent-board
+```
+
+## Quick Start
+
+Open the board with `/agent-board` inside Pi, or press `Left` twice on an empty prompt, then:
+
+1. Press `i` to enter INSERT mode.
+2. Type a task.
+3. Press `Enter`. It starts right away in the current folder, with this session's model and thinking level.
+
+To choose the folder, model or thinking level first, press `Ctrl+N` while typing. With an empty input, `Enter` attaches/resumes the selected session. The row starts in `Queued`, then moves through `Running` to a terminal state such as `Needs answer`, `Needs instructions`, `Done`, `Failed`, or `Stopped`.
+
+From the board:
+
+- Press `Space` to peek at the selected session's summary, blocker, and latest output.
+- In Peek, press `r` to reply without attaching.
+- Press `v` for a read-only transcript, or `e` for evidence and diagnostics.
+- Press `Enter`, `Right`, or `>` to attach to the real Pi session.
+- In PTY attach mode, press `Ctrl+Left` to return to the board at any time (even mid-draft), or `Ctrl+\` — the unconditional escape: it detaches regardless of editor state on any terminal that forwards the raw 0x1c byte (raw, kitty, and modifyOtherKeys keyboard modes all work). `Left` detaches only while the child Pi reports an empty editor; otherwise (draft, or unknown editor state) it is forwarded to the child. `Ctrl+]` is not a detach key — it is passed through to the child Pi editor. When the host is disconnected, `Left` always exits. `Ctrl+\` caveats: on keyboard layouts where `\` sits on AltGr (e.g. German) the chord may never produce the byte — use `Ctrl+Left` there; in legacy keyboard modes `Ctrl+4` emits the same byte and also detaches; and the key is captured from the child while attached, so the child's own `Ctrl+\` binding (e.g. the vim terminal-mode prefix) is unavailable. Automatic themes also resolve correctly in attach sessions: the child's background probe (OSC 11) and color-scheme change notifications are forwarded to your real terminal, replies flow back to the child when your terminal answers, and attach re-probes the background once when it settles so the theme is right from the first frame. Set `AGENT_BOARD_FORWARD_TERMINAL_QUERIES=0` to disable this (default on); keyboard-protocol negotiation (kitty/DA) is not forwarded — it happens once at child spawn, before attach exists. `Ctrl+X` opens an in-place delete confirm: press `y` (or Enter) to archive the row and return to the board with the next row selected — any other key cancels and is passed through to the session. While attached, the child Pi's own `Ctrl+X` bindings (copy in `/tree` and fullscreen, clear-all in the models dialog) are captured by this gesture.
+
+## Dashboard Workflow
+
+The dashboard has two input modes:
+
+- **Normal mode** owns dashboard shortcuts such as navigation, peek, attach, and filtering.
+- **INSERT mode** owns text editing. Press `i` before typing or pasting a task; `/` is literal while editing a prompt.
+
+When you press `Ctrl+N` while typing a task, the **Start session** dialog lets you review:
+
+- `cwd`: an existing-directory picker with usage-ranked favorites, filesystem browsing, and Tab completion;
+- `model`: models available to Pi, including models scoped by the current directory's Pi settings;
+- `thinking`: a level supported by the selected model;
+- `action`: **start in background** or **start & attach**.
+
+Launch preferences are persisted and reused for later sessions. **Start & attach** requires PTY support; if PTY is unavailable, Agent Board launches the session in the background and shows a warning instead.
+
+Session actions are deliberately confirmation-aware:
+
+- `d` confirms moving an inactive session to **Done**. Manual completion is the default.
+- `h` toggles the on-hold state (manual verdict — automated writers are fenced).
+- Press `x`, then `y` to confirm deleting the selected row. `Ctrl+X` twice quickly still deletes without confirmation. Archiving removes the row from the board but preserves its underlying Pi session file.
+- `X` archives inactive rows in the selected state; live work is skipped.
+- `m` enters multi-select mode; see [Multi-select](#multi-select) for its keys.
+
+## Views and Actions
+
+Shortcuts are scoped to the view where they are available:
+
+### Main list
+
+| Key | Action |
+| --- | --- |
+| `Up` / `Down` / `j` / `k` | Move the selection. |
+| `i` | Enter INSERT mode for a new task. |
+| `Enter` | Start a draft right away, or attach/resume when the input is empty. |
+| `Right` / `>` / `l` | Attach to the selected session. |
+| `Space` | Open Peek. |
+| `v` | Open the read-only transcript. |
+| `e` | Open Evidence / Diagnostics. |
+| `/` | Enter filter mode. |
+| `Ctrl+N` | Enter INSERT mode with a pre-filled `hello` prompt. |
+| `Left` twice | From an empty Pi prompt, open the board. |
+| `Ctrl+R` | Rename the selected session. |
+| `Ctrl+T` | Pin or unpin the selected session. |
+| `Ctrl+S` | Stop the selected active session. |
+| `d` | Confirm marking the selected inactive session Done. |
+| `h` | Hold or unhold the selected inactive session. |
+| `x`, then `y` | Archive/delete the selected row (confirmation prompt). |
+| `Ctrl+X` twice quickly | Archive/delete the selected row without confirmation. |
+| `X` | Delete inactive rows in the selected state. |
+| `m` | Enter multi-select mode. |
+| `!` | Open node-pty diagnostics and fix steps. |
+| `?` | Open the help overlay. |
+| `Esc` | Clear a draft, or exit when the input is empty. |
+
+### Multi-select
+
+Press `m` in the main list to act on several sessions at once.
+
+| Key | Action |
+| --- | --- |
+| `Up` / `Down` / `j` / `k` | Move the selection. |
+| `Space` | Toggle the current row. |
+| `a` | Select all visible rows. |
+| `u` | Clear the selection. |
+| `d` | Confirm marking the selected inactive rows Done. |
+| `Ctrl+X` | Delete the selected Done rows (confirmation prompt). |
+| `m` / `Esc` / `Ctrl+C` | Leave multi-select mode. |
+| `?` | Open the help overlay. |
+| `!` | Open node-pty diagnostics and fix steps. |
+
+### Peek
+
+Peek shows the selected session's summary, blocker or question, latest output, and available issue/PR references.
+
+| Key | Action |
+| --- | --- |
+| `r` or `Enter` | Enter reply mode; type a follow-up and press `Enter` to send it without attaching. |
+| `a`, `Right`, `>`, or `l` | Attach to the session. |
+| `v` | Open the read-only transcript. |
+| `e` | Open Evidence / Diagnostics. |
+| `d` | Confirm marking the inactive session Done. |
+| `h` | Hold or unhold the session. |
+| `!` | Open node-pty diagnostics and fix steps. |
+| `Up` / `Down` / `j` / `k` | Move to the previous or next session. |
+| `Esc` | Return to the main list. |
+
+When a Pi question or questionnaire tool is pending, inline reply is rejected; attach to answer that interactive question in the real Pi session.
+
+### Transcript
+
+The `v` view is a read-only projection of the durable Pi session JSONL. It does not interrupt a running worker.
+
+| Key | Action |
+| --- | --- |
+| `Up` / `Down` / `j` / `k` | Scroll one line. |
+| `PageUp` / `PageDown` | Scroll one page. |
+| `Space` | Open Peek. |
+| `r` | Enter reply mode. |
+| `Enter` or `a` | Attach to the session. |
+| `e` | Open Evidence / Diagnostics. |
+| `d` | Confirm marking the inactive session Done. |
+| `h` | Hold or unhold the session. |
+| `!` | Open node-pty diagnostics and fix steps. |
+| `Left` / `Esc` / `<` | Return to the main list. |
+
+### Evidence / Diagnostics
+
+The `e` view shows durable session evidence, including changed files, commands and their outcomes, command output previews, assistant evidence, errors, diagnostics, and artifact paths. Press `x` to clear diagnostics while preserving the evidence artifacts.
+
+| Key | Action |
+| --- | --- |
+| `Up` / `Down` / `j` / `k` | Scroll one line. |
+| `PageUp` / `PageDown` | Scroll one page. |
+| `r` | Enter reply mode. |
+| `v` | Open the read-only transcript. |
+| `Enter`, `a`, `Right`, or `l` | Attach to the session. |
+| `x` | Clear diagnostics; evidence is preserved. |
+| `Left` / `Esc` / `<` | Return to the main list. |
+
+### PTY attach
+
+PTY attach opens the real interactive Pi session. `Ctrl+Left` detaches and returns to the board regardless of editor state, and `Ctrl+\` is the unconditional escape — a single raw ASCII byte (0x1c) that terminals forward unchanged in raw mode (kitty CSI-u and modifyOtherKeys encodings included), honored no matter what the child editor reports. `Left` detaches only while the child Pi reports an empty editor; while you are editing text — or when the child's editor state is unknown (e.g. the child extension is missing) — `Left` is forwarded to the Pi editor. A disconnected host can always be exited with `Left`. `Ctrl+]` is not a detach key — it is passed through to the child Pi editor. `Ctrl+\` caveats: on keyboard layouts where `\` sits on AltGr (e.g. German) the chord may never produce the byte — use `Ctrl+Left` there; in legacy keyboard modes `Ctrl+4` emits the same byte and also detaches; and the key is captured from the child while attached, so the child's own `Ctrl+\` binding (e.g. the vim terminal-mode prefix) is unavailable. While attached, `PageUp`, `PageDown`, `Home`, `End`, and the mouse wheel scroll local scrollback; whenever that viewport cannot move — the session holds the alternate screen (pi's fullscreen default), or there is no local history to travel — the wheel is forwarded to the session instead, which scrolls its own transcript: the same fallback the paging keys use. The attach viewport only scrolls scrollback the hosted session actually produced: rows that a snapshot hydration had to scroll out of the local window are not history, and the wheel is forwarded to the session instead of consuming those rows. Mouse drag or double-click selects and copies text, clicks open detected links, and middle-click paste is available on systems with the required X11 tooling. `Ctrl+X` opens an in-place delete confirm: press `y` (or Enter) to archive the row and return to the board with the next row selected — any other key cancels and is passed through to the session. While attached, the child Pi's own `Ctrl+X` bindings (copy in `/tree` and fullscreen, clear-all in the models dialog) are captured by this gesture.
+
+Automatic light/dark themes work in attach sessions too. The child Pi's background-color probe (OSC 11) and its color-scheme change notification switch are forwarded to your real terminal; replies and notifications flow back to the child when your terminal answers — a terminal that never answers keeps the dark fallback. Attach also re-probes the background once when it settles, so the theme is correct from the first frame without re-selecting it in `/settings`. All of this is on by default; set `AGENT_BOARD_FORWARD_TERMINAL_QUERIES=0` to disable it. Not covered: keyboard-protocol negotiation (kitty flags / DA1) is not forwarded — the child negotiates once at spawn, before any attach client exists, and forwarding it would retune the shared real-terminal keyboard stack — so modifier-key encoding can still differ from a directly-run Pi (the modifyOtherKeys fallback applies).
+
+The attach surface can forward terminal clipboard and image/file passthrough sequences. These behaviors can be disabled individually in [Configuration](#configuration). Cold hosts may briefly show a loading/reconnect surface while their PTY becomes ready.
+
+## States, Grouping, and Filters
+
+Agent Board separates a session's semantic task state from whether a worker process is currently alive. An exited worker can therefore leave a durable row that is still resumable or attachable.
+
+| Display state | Meaning |
+| --- | --- |
+| **Queued** | A run has been scheduled but has not started processing. |
+| **Running** | The session is actively processing. |
+| **Needs answer** | The session is waiting for user input or an answer to a question. |
+| **Needs instructions** | The run ended without being marked complete and needs the next directive. |
+| **On hold** | The user parked this session intentionally (manual verdict, `h` to toggle). Automated writers can't push it to Done; queued follow-ups do not wake it. |
+| **Done** | The user marked the inactive session complete; this is the default completion path. |
+| **Failed** | The worker or host ended with an error. |
+| **Stopped** | The user stopped the active work. |
+
+Rows are grouped by state. When a state contains sessions from multiple directories, rows are grouped by folder within that state. Pinned rows and folders come first, then creation order remains stable; activity does not reshuffle the list. New agent activity is marked unread with stronger row glyphs and header/footer counts. Replies sent while a session is busy enter a durable FIFO follow-up queue and are delivered when the session is ready; a `qN` badge shows queued follow-ups.
+
+Press `/` to enter filter mode. Filter tokens are case-insensitive and can be combined with free-text terms:
+
+```text
+s:running
+s:hold
+review:ready
+diag:stalled
+evidence:error
+queued:true
+steer:awaiting-approval
+```
+
+- `s:<state>` matches a state prefix, including display-label aliases such as `needs-answer`.
+- `review:ready` finds sessions with review-ready evidence.
+- `evidence:error` finds sessions whose evidence contains errors.
+- `queued:true` (also `yes` or `1`) finds sessions with queued follow-ups.
+- `steer:<state>` filters by a persisted steering state.
+- Bare words match name, summary, and working directory; multiple words use AND matching.
+
+`diag:stalled` can consume persisted stalled diagnostics, but the current runner does not provide a general provider-stall detector. It should not be read as a complete automatic stall-detection feature.
+
+## Evidence and Code References
+
+Evidence is collected locally from session events. Agent Board can extract issue and pull-request references from that evidence and show badges such as `#40` or `▸#45` on rows; Peek includes the provider, confidence, source, and URL when available. Built-in GitHub/GitLab-style providers are available, and an optional per-store `providers.json` can extend the provider rules. The `AGENT_BOARD_CODE_REFS=off` setting disables extraction.
+
+For internal code platforms (non-github/gitlab hosts) or custom CLIs, add a per-store `providers.json` so claim/action rules exist and sessions stop depending on the low-confidence mention fallback. Example — an internal CLI (`acli`) with claim-strength issue rules:
+
+```json
+{
+  "providers": [
+    {
+      "name": "acode",
+      "hosts": ["acode.internal.example.com"],
+      "rules": [
+        { "pattern": "acli\\s+issue\\s+update\\s+#?(\\d+)(?=[\\s\\S]*--assignee)", "kind": "issue", "strength": "claim" },
+        { "pattern": "acli\\s+issue\\s+(?:note|comment|close)\\s+#?(\\d+)", "kind": "issue", "strength": "action" },
+        { "pattern": "acli\\s+issue\\s+(?:show|view)\\s+#?(\\d+)", "kind": "issue", "strength": "view" }
+      ]
+    }
+  ]
+}
+```
+
+`hosts` matches the repo's remote host; rules follow the same `pattern`/`kind`/`strength` shape as the built-in `gh`/`glab` tables (`strength`: `claim` > `action` > `view`), and the `#N` capture group supplies the number. Validation errors from a broken file surface in the diagnostics panel and never break extraction — an invalid file is simply ignored.
+
+## Attach and Fallback Behavior
+
+When PTY support is healthy, Agent Board uses an interactive PTY host for attach and start-and-attach. If PTY support is unavailable, eligible managed sessions can still run in the background through the JSON runner; start-and-attach falls back to background launch with a warning. Adopted external foreground sessions require PTY to continue safely. Press `!` in the dashboard for diagnosis and fix steps.
+
+On Windows, PTY host control uses a named pipe and spawned child console windows are hidden. Terminal behavior can still vary between terminal emulators.
+
+## Entry Points
+
+| Entry point | What it does |
+| --- | --- |
+| `/agent-board` | Opens the dashboard from an interactive Pi session. Use this command path to attach to managed sessions. |
+| `pi /agent-board` | Starts Pi by invoking the dashboard command. Quitting the standalone dashboard shuts down Pi instead of dropping into a normal chat session. |
+| `pi --agent-board` | Opens the dashboard through the extension startup flag. This startup path cannot attach to a managed session; use `/agent-board` from a normal Pi session for attach. |
+| `/bg [prompt]` | Adopts the current interactive Pi session into Agent Board. An optional prompt is added to its follow-up queue before the dashboard opens. |
+
+The board is global across projects by default. Rows are stored under `~/.pi/agent/agent-board/`; archiving a row removes it from the board but preserves the underlying Pi session file.
+
+## Persistence, Safety, and Limitations
+
+Agent Board stores its durable roster and per-session artifacts under `~/.pi/agent/agent-board/` by default. Set `AGENT_BOARD_ROOT` to use another location. The store includes the roster, launch preferences, per-session metadata and state, Pi session JSONL, run status/events, evidence, diagnostics, and (for PTY hosts) a replayable screen log.
+
+Rows and session history survive Pi reloads, Pi restarts, and worker exits. When the dashboard opens, it reconciles stale runner or host records and keeps resumable sessions visible. Archiving a row removes it from the board but does not delete its underlying Pi session file.
+
+> **Worktree isolation is currently disabled.** Agent Board does not automatically create or manage Git worktrees. Multiple sessions in the same repository may run concurrently, so avoid overlapping writes or provide your own isolation before starting parallel coding tasks.
+
+Other current limitations:
+
+- Agent Board runs locally; it does not provide cloud execution, multi-user coordination, or shared dashboards.
+- Real model output still depends on Pi provider authentication and network access.
+- The `--agent-board` startup path opens the dashboard but cannot attach to a managed session; use `/agent-board` from a normal Pi session for attach.
+- Pending Pi question or questionnaire tools must be answered in the attached interactive session; inline reply is rejected while one is pending.
+- PTY-dependent features require a working `node-pty` installation. Background work can use the JSON-runner fallback when PTY is unavailable, but start & attach then becomes background-only.
+
+## Configuration
+
+Set these variables before starting Pi. Model-backed features fall back gracefully where noted, so disabling them does not prevent the core dashboard from working.
+
+| Variable | Default / values | Purpose |
+| --- | --- | --- |
+| `AGENT_BOARD_ROOT` | `~/.pi/agent/agent-board/` | Override the durable store location. |
+| `AGENT_BOARD_AUTO_STATE` | enabled; `off` disables | Enable automatic terminal-state refinement after a turn. |
+| `AGENT_BOARD_AUTO_STATE_MODEL` | `gpt-4o`; `off` uses heuristics | Model for classifying the terminal state of a finished turn. |
+| `AGENT_BOARD_AUTO_STATE_NO_DONE` | unset = manual Done; `0`, `false`, `off`, or `no` restores auto-Done | Keep completion manual by default, or restore automatic `Done` classification. |
+| `AGENT_BOARD_SUMMARY_MODEL` | `gpt-4o`; `off` disables | Generate short row summaries. Heuristic summaries remain available as a fallback. |
+| `AGENT_BOARD_TITLE_MODEL` | `openai-codex/gpt-5.5`; `off` disables | Generate a short session title after dispatch. The initial slug remains if generation fails. |
+| `AGENT_BOARD_TITLE_THINKING_LEVEL` | `low`; `off` omits the option | Thinking level used by title generation. |
+| `AGENT_BOARD_CODE_REFS` | enabled; `off` disables | Extract issue/PR badges from session evidence. |
+| `AGENT_BOARD_DISABLE_PTY` | unset; `1` disables | Disable PTY host and attach mode. |
+| `AGENT_BOARD_FORCE_PTY` | unset; `1` forces the PTY path | Force the PTY availability path when diagnosing or controlling fallback behavior. |
+| `AGENT_BOARD_ATTACH_MOUSE` | enabled; `0`, `off`, or `false` disables | Disable attach-view mouse handling and use terminal-native selection instead. |
+| `AGENT_BOARD_ENABLE_MOUSE_SCROLL` | enabled; `0` disables | Compatibility switch to disable attach-view mouse scrolling. |
+| `AGENT_BOARD_WHEEL_LINES` | `1`, clamped to `1..50` | Lines scrolled per mouse-wheel notch in the attach view (regular TUI mode; in fullscreen the TUI's own wheel accelerator decides the line count). |
+| `AGENT_BOARD_MAX_WARM_HOSTS` | `4`, clamped to `0..50` | Maximum number of idle PTY hosts retained for faster attach. |
+| `AGENT_BOARD_WARM_HOST_TTL_MS` | `600000` (10 minutes); `0` disables TTL eviction | How long an idle warm host may remain before it is evicted. |
+| `AGENT_BOARD_ATTACH_NATIVE_PASTE` | enabled; `0` disables | Disable X11 PRIMARY selection copy and middle-click paste integration. |
+| `AGENT_BOARD_FORWARD_OSC52` | enabled; `0` disables | Disable OSC 52 clipboard sequence forwarding from an attached session. |
+| `AGENT_BOARD_FORWARD_IMAGES` | enabled; `0` disables | Disable terminal image/file passthrough forwarding from an attached session. |
+| `AGENT_BOARD_IME_FIX` | enabled; `0` disables | Disable the attach-view IME cursor coalescer if your terminal has compatibility problems. |
+| `AGENT_BOARD_TERMINAL_SNAPSHOT` | enabled; `0` forces legacy | Force the pre-phase-4 attach path (screen.log replay + jiggle); escape hatch / rollback switch for the snapshot+subscribe attach protocol. |
+| `AGENT_BOARD_REPLY_GUARD` | enabled; `0`, `off`, or `false` disables | Discard terminal reply fragments (device attributes, kitty flags, cell size, DCS) that pi-tui delivers as input, and forward color replies whole. While a reply head is open, up to 64 bytes / 250ms of following input is absorbed. |
+
+`AGENT_BOARD_TERMINAL_SNAPSHOT=0` routes attach onto the legacy fallback family: the screen.log replay tail plus the shrink-and-hold jiggle redraw. These paths exist only for pre-protocol runners and as a rollback hatch — they are not part of the snapshot+subscribe protocol path (issue #91 phase 4). They will be retired once the installed runner fleet is on the snapshot protocol baseline (detectable on the wire via hello protocol fields).
+
+Older `AGENT_VIEW_*` names are still read in selected compatibility paths. Prefer `AGENT_BOARD_*` for new setups. Internal child markers are managed by Agent Board and are not user settings.
+
+The `providers.json` file under the configured store root can extend the built-in issue/PR reference providers; see the [Evidence and Code References](#evidence-and-code-references) section for the feature overview.
+
+## Troubleshooting
+
+### Rows stay in `Running`
+
+First verify that Pi itself can complete a one-shot model call:
+
+```bash
+pi --mode json -p --no-session "Reply with exactly: DONE"
+```
+
+The command should emit an assistant reply, then an `agent_end` event, and exit. If it hangs before the assistant reply, fix Pi provider authentication or network access first. Agent Board cannot produce live model results until Pi works independently.
+
+### `node-pty unavailable`
+
+Press `!` in the dashboard to open the diagnostic panel and follow its fix steps. Common causes include a missing native `node-pty` binary, a Node/architecture mismatch, a missing or non-executable macOS `spawn-helper`, or macOS quarantine. You can temporarily set `AGENT_BOARD_DISABLE_PTY=1` to use background JSON-runner behavior where supported.
+
+### Attach is slow or keeps reconnecting
+
+A cold PTY host may briefly show a loading or reconnecting surface while it starts. Check the PTY status in the dashboard with `!`; stale hosts are diagnosed separately from active task workers. If the host never becomes healthy, repair `node-pty` or use background mode for eligible managed sessions.
+
+### IME candidate window is stuck at the window edge (Windows WezTerm)
+
+On Windows WezTerm with a WSL2 backend, the IME candidate window may stay pinned to the right edge instead of following the text cursor in an attached session. Windows WezTerm only tracks the IME candidate position from the visible hardware cursor, and Pi hides the hardware cursor by default — the block cursor you see in the editor is drawn content, not the hardware cursor. Linux terminals are not affected.
+
+Make the hardware cursor visible, either way:
+
+```bash
+export PI_HARDWARE_CURSOR=1    # machine-local, e.g. ~/.zshrc.local
+```
+
+or set `"showHardwareCursor": true` in Pi's `settings.json` (syncs across machines if the config is version-controlled; harmless on Linux).
+
+Trade-off: the real terminal cursor becomes visible inside the TUI. This is cosmetic only.
+
+### Start & attach falls back to background
+
+Start & attach requires PTY support. When PTY is unavailable, the task is still dispatched in the background and the dashboard displays a warning. Repair PTY and retry attach from the normal `/agent-board` command path.
+
+### Inline reply is rejected
+
+A pending Pi question or questionnaire requires the real interactive session. Attach to the row and answer it there; ordinary replies can be sent from Peek and are queued while a session is busy.
+
+### Sessions in the same repository conflict
+
+Worktree isolation is not enabled. Stop overlapping writers, separate their working directories, or create and manage Git worktrees yourself before running concurrent coding tasks.
+
+See [VERIFY.md](VERIFY.md) for no-auth checks, extension loading checks, provider checks, persistence checks, and the manual dashboard flow.
+
+## Development
+
+For local development:
+
+```bash
+npm install
+npm run verify
+```
+
+`npm run verify` runs typecheck, the perf gate (`npm run test:perf`), tests, coverage, and a package dry-run. The A11 perf assertions are opt-in — they skip under `npm test` / `npm run test:coverage` and only measure via `npm run test:perf` (issue #121). The same checks run in CI on Node 22 and Node 24. See [VERIFY.md](VERIFY.md) for the full verification checklist and known environment-dependent limitations.
+
+## Publishing
+
+Releases run through `scripts/release.mjs` and are published by CI when a GitHub Release is created. The flow checks the parts that are easy to get wrong — the changelog range, tag ancestry against `main`, and drift from a late merge — instead of assuming them. See [docs/RELEASE.md](docs/RELEASE.md) for the full process, the one-time npm trusted-publisher setup, and failure recovery.
+
+```bash
+node scripts/release.mjs precheck          # gate: clean main, nothing in flight
+node scripts/release.mjs prepare minor     # changelog + verify + bump + tag + release branch
+node scripts/release.mjs open-pr 0.9.0     # push the branch and tag, open the release PR
+# merge the PR with a merge commit, then:
+node scripts/release.mjs finish 0.9.0      # GitHub Release → CI publishes to npm
+```
+
+After publishing, users install the scoped package with:
+
+```bash
+pi install npm:@huseynsnmz/pi-board
+```
+
+The Pi package gallery uses the `pi.video` and `pi.image` URLs from `package.json`.
+
+## Further Reading
+
+- [Manual verification](VERIFY.md) — static checks, Pi loading, provider authentication, persistence, and dashboard flows.
+- [Release process](docs/RELEASE.md) — release commands, trusted publishing setup, and failure recovery.
+- [Product requirements](PRD.md) — original product scope and design context.
+- [Progress log](PROGRESS.md) — implementation checkpoints and known environment notes.
+- [Exploration notes](docs/EXPLORATION.md) — Pi API and integration research.

package/VERIFY.md

@@ -0,0 +1,115 @@
+# Manual Verification
+
+Steps you can run yourself to check the extension. Grouped from "no auth needed" to
+"needs pi provider auth". Commands assume you're in the repo root.
+
+---
+
+## 0. Static checks (no auth, fast)
+
+```bash
+npm install          # dev + runtime deps
+npm run typecheck    # expect: 0 errors
+npm run test:perf    # expect: `burst:`/`paced:` value lines, pass 3 / skipped 0 — the ONLY path that measures perf assertions; they skip under npm test (issue #121)
+npm test             # expect: 0 failures (the 3 A11 perf tests skip here, reason points at `npm run test:perf`)
+npm run pack:dry     # expect: pi-agent-board-<version>.tgz contents only include deploy files
+```
+
+`npm test` includes a hermetic integration test that runs the **real detached runner** against
+a fake pi worker (`test-support/fake-pi.mjs`) — it proves dispatch → events → status/state →
+finalize (completed / needs_input / failed / stopped) without any model/network.
+
+## 1. Does the extension load in pi? (no auth)
+
+```bash
+pi --list-models -e "$(pwd)/src/index.ts"
+```
+Expect a normal model table and **exit 0** (the extension factory ran without throwing). If you
+see an error mentioning `index.ts` / jiti / a missing import, that's a load problem.
+
+## 2. CRITICAL: can pi reach a model at all? (needs pi auth)
+
+This is the thing that was blocked in the dev sandbox. The background worker is just
+`pi --mode json -p --session <file> "<prompt>"`, so first confirm a plain one-shot works:
+
+```bash
+# Should print a JSON event stream that ENDS WITH a line of type "agent_end", then exit
+# within a few seconds. Watch for an "assistant" message_end before agent_end.
+pi --mode json -p --no-session "Reply with exactly: DONE" | tail -n 20
+```
+- ✅ **Healthy:** you see `...message_end (assistant)...`, then `agent_end`, and the command exits.
+- ❌ **Hang:** it prints up to a `message_end` for the **user** message then sits idle (no
+  assistant reply, never exits). That means pi has no working provider auth / network here.
+  Fix pi's auth first:
+  ```bash
+  pi            # then run /login inside pi, or set the provider key pi expects, e.g.
+  # export ANTHROPIC_API_KEY=...   (or OPENAI_API_KEY=... for gpt-4o summaries)
+  ```
+  Re-run the one-shot above until it ends in `agent_end`. The dashboard cannot show live results
+  until this works — it's a pi setup step, independent of this extension.
+
+## 3. Install the extension for normal use
+
+For a local checkout, install it as a Pi package:
+```bash
+pi install "$(pwd)"
+```
+Or symlink the repo into pi's global extensions dir (auto-discovered via the top-level `index.ts`):
+```bash
+ln -s "$(pwd)" ~/.pi/agent/extensions/agent-board
+```
+After publish, install with:
+```bash
+pi install npm:@zhuxixi/pi-agent-board
+```
+Then start pi normally:
+```bash
+pi
+```
+
+## 4. Drive the dashboard
+
+Inside pi:
+1. Type `/agent-board`, or start with `pi /agent-board` → the full-screen dashboard opens.
+   - With `pi /agent-board`, quitting the dashboard exits Pi instead of dropping you into a normal chat session.
+   - The startup path should feel cleaner than `/agent-board`: no normal Pi header/footer chrome and no dispatch notifications above the dashboard.
+2. Press **i** to enter INSERT mode, then type a task in the bottom input (e.g. `list the files in this repo and summarize the README`) and press **Enter**.
+   - A **Start session** dialog opens with **Start session** focused by default.
+   - Press **Enter** again to launch immediately, or move with **↑/↓** to change **cwd**, **model**, or **thinking** first.
+   - With automatic Done disabled by default, a successful run settles in **Needs instructions** until you review it and press **d** to confirm **Done**. Set `AGENT_BOARD_AUTO_STATE_NO_DONE=0` to restore automatic Done classification for this verification path.
+3. **space** = peek when the input is empty (summary, blocker, latest output); in peek **r** = reply, **a** = attach.
+   **→** / **>** = open a full-screen live session view without interrupting; **←** / **<** returns.
+4. **enter** on an empty input = attach to the selected full session (confirms first if it's still running).
+   You're now in the real Pi session; run `/agent-board` again to return.
+5. Other keys: **/** filter (`s:running`, or free text), **Ctrl+R** rename, **Ctrl+T** pin, **Ctrl+S** stop,
+   **x** then **y** delete (confirm prompt; archives the row, keeps the session file), **Ctrl+X** ×2 quick delete (no confirm),
+   **?** help, **Esc** clears input / quits when empty.
+
+## 5. Inspect the durable store on disk
+
+```bash
+ls -R ~/.pi/agent/agent-board
+cat ~/.pi/agent/agent-board/roster.json
+cat ~/.pi/agent/agent-board/views/*/state.json
+cat ~/.pi/agent/agent-board/views/*/runs/*/status.json
+# raw worker event stream for a run:
+cat ~/.pi/agent/agent-board/views/*/runs/*/events.jsonl
+```
+
+## 6. Recovery / persistence
+
+- Start a dispatch, then quit pi (or `/reload`). Re-open pi and `/agent-board` — the row is still
+  there with its last state (rehydrated from disk). If a run's runner died without finishing,
+  the dashboard reconciles it to `failed (runner exited)` on open.
+
+## 7. Same-repo session launches
+
+- Dispatch one task in a git repo, then (while it's running) dispatch a second in the
+  **same repo**. Both launches should be allowed. The extension never creates a git worktree on
+  its own.
+
+## 8. Summary model
+
+Default summary model is **gpt-4o** (override `AGENT_BOARD_SUMMARY_MODEL=<model>`, disable with
+`AGENT_BOARD_SUMMARY_MODEL=off`; legacy `AGENT_VIEW_SUMMARY_MODEL` is also honored). It needs OpenAI auth; without it the row keeps its heuristic
+summary (e.g. the first sentence of the agent's last message or the active tool).