@huseynsnmz/pi-suite 0.0.0-stage → 0.2.0

package/packages/board/README.md

@@ -0,0 +1,88 @@
+# pi-board
+
+Part of [pi-suite](../../README.md). Turn it off with `/suite off board`.
+
+A board for [Pi](https://pi.dev)'s background sessions: start a task and keep working, see which sessions need you, peek at them, reply, and attach when you want the whole conversation. The keys follow Claude Code's agent view.
+
+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.
+
+```text
+╭─ π-board 0.16.0 ────────────────────────────── node-pty healthy · hosts:2 ─╮
+│ 1 needs answer · 1 running · •1 unread · 0 done                            │
+╰────────────────────────────────────────────────────────────────────────────╯
+◇ NEEDS ANSWER 1 ─────────────────────────────────────────────────────────────
+ ›◆ fix the login test     my-app       Waiting on a prompt                 2m
+● RUNNING 1 ──────────────────────────────────────────────────────────────────
+  ● update the changelog   my-app       Running git log                    12s
+╭─ new session ──────────────────────────────────────────────────────────────╮
+│ › type a task to start a session                                           │
+╰─ enter resume   space peek   ctrl+f filter   ctrl+x stop   ? keys ─────────╯
+```
+
+## Quick start
+
+Requires Pi 1.5 or newer.
+
+1. Install it:
+
+   ```bash
+   pi install npm:@huseynsnmz/pi-suite@0.1.0
+   ```
+
+2. Restart Pi, and press `Left` twice on an empty prompt, or run `/agent-board`.
+3. Type a task and press `Enter`. It starts right away in the selected session's folder, shown on the input's title, with this session's model. With no sessions, that's this folder.
+
+Your current session becomes a row too, even with no messages yet. `Esc`, or `Enter` on its row, brings you back to it.
+
+Installing it runs `node-pty`'s install script, which sets up its terminal support.
+
+## Keys
+
+| Key | Action |
+| --- | --- |
+| Any text | Start writing a task |
+| `Enter` | Start the task, or attach to the selected session |
+| `Left` / `Right` | Attach to the selected session |
+| `Ctrl+\` | Back to the board from a session. `Left` also works on an empty prompt |
+| `Space` | Peek at a session, and type there to reply |
+| `/` | Pi's commands, as at the prompt. Templates and skills start a session |
+| `Ctrl+F` | Filter |
+| `Ctrl+X` | Stop a session, and press again within 2 seconds to delete it |
+| `Ctrl+N` | While typing, choose the folder, model and thinking level |
+| `!` | `node-pty` diagnostics |
+| `?` | All the keys |
+| `Esc` | Clear the input, or leave the board |
+| `Ctrl+C` twice | Quit Pi, from the board or a session. Sessions keep running |
+| `Ctrl+Z` | Put Pi in the background, from the board or a session, and `fg` brings it back. Sessions keep running |
+
+The full list is in the [reference](docs/reference.md).
+
+## Settings
+
+Settings live in `~/.pi/agent/extensions/pi-board/config.json`.
+
+The board can use a model for titles, row summaries and working out what state a session is in. That's **off by default**, and built-in rules do the job instead. To choose a model, run `/board-model`. Helper calls cost tokens, and send up to 6,000 characters of a session's latest reply to that model.
+
+## Good to know
+
+- **No worktrees:** sessions in one repository share its files, so give each writer its own worktree.
+- **Sessions outlive Pi:** closing Pi leaves them running. That's the point, but idle ones are only cleaned up by a timer or the next board activity.
+- **Answering prompts:** a session waiting on a permission prompt shows `Needs answer`, and you attach to answer it. A reply from Peek waits in the queue.
+- **Saved to disk:** sessions and a screen log are plain files under `~/.pi/agent/agent-board/`.
+
+More detail is in [How it works](docs/how-it-works.md) and the [reference](docs/reference.md).
+
+## `pi-frame`
+
+[`pi-frame`](https://github.com/huseynsnmz/pi-suite/tree/main/packages/frame) 0.3.8 or newer draws its header and footer again when the board closes.
+
+## Contributing
+
+Issues are welcome, and pull requests are turned off. See [CONTRIBUTING.md](CONTRIBUTING.md) and [SECURITY.md](SECURITY.md).
+
+## Credits and license
+
+MIT. See [LICENSE](LICENSE), which keeps the original copyright notice.
+
+- [pi-agent-board](https://github.com/zhuxixi/pi-agent-board) by zhuxixi and its contributors
+- The keys and layout follow [Claude Code's agent view](https://code.claude.com/docs/en/agent-view).

package/packages/board/SECURITY.md

@@ -0,0 +1,19 @@
+# Security
+
+## Reporting a vulnerability
+
+Please don't open a public issue for a security problem. Use **Report a vulnerability** on the repository's Security tab, or email huseyin@snmz.org.
+
+Examples that count as security problems:
+
+- A reply or other input from the board that answers a permission prompt in a session.
+- Output from a session that reaches your terminal as a command, or runs anything outside that session.
+- Another local user reaching a session through the board's sockets or files.
+
+Fixes go into the latest release only.
+
+## What this extension does not protect against
+
+- **What a session can do:** each one is a real Pi session with your access. Use your permission rules and sandbox.
+- **Project files:** a trusted project's Pi settings apply to its sessions.
+- **Secrets on screen:** anything printed in a session is saved in its session file and screen log.

package/packages/board/docs/how-it-works.md

@@ -0,0 +1,31 @@
+# How it works
+
+Every session on the board is a real Pi session, running in a terminal the board keeps open for it.
+
+```text
+/agent-board (a screen inside your Pi)
+   │ start a task
+   ▼
+detached runner ──→ real `pi` in a hidden terminal (node-pty)
+   │                 ├─ your extensions, permissions and session file
+   │                 └─ keeps running after you close Pi
+   ▼
+~/.pi/agent/agent-board/ ──→ the board reads state from here
+```
+
+- **Starting a task:** a detached runner starts Pi at a saved session file, and types your task into it.
+- **State:** the extension also loads inside each session, and reports what it's doing to a small coordinator process, which is the only writer of each row's state. The board reads that.
+- **Waiting on you:** a permission prompt or other dialog takes the keyboard from Pi's prompt during a run, and that puts the row in `Needs answer`. A reply from Peek waits in the queue, because typing into the session would answer the dialog.
+- **Attaching:** the board shows the session's real terminal inside your Pi, and hands the keyboard over until you detach.
+- **The session you're in:** pressing `Left` twice adds its session file as a row. Pi keeps running it, so the board never starts a second Pi on that file.
+- **Without node-pty:** tasks run with `pi --mode json -p`, where nothing can answer a prompt, and you can't attach.
+
+## What it costs
+
+The board makes no model calls of its own unless you choose a helper model with `/board-model`. See the [reference](reference.md#helper-model).
+
+## What it doesn't do
+
+- **Isolate sessions:** sessions in one repository share its working tree, so they can overwrite each other. Use your own worktrees for parallel changes.
+- **Sandbox anything:** each session has what any Pi session has, with your extensions and permissions.
+- **Protect what's on screen:** session files and a replayable screen log are stored as plain files, so a secret printed in a terminal gets saved.

package/packages/board/docs/reference.md

@@ -0,0 +1,278 @@
+# Reference
+
+## Main list
+
+Typing goes straight into the input, as in Claude Code's agent view, so there's no mode to enter first.
+
+| Key | Action |
+| --- | --- |
+| Any text | Start writing a task. |
+| `Enter` | Start the task, or attach to the selected session when the input is empty. |
+| `Ctrl+Enter` | Start the task and attach to it. |
+| `Shift+Enter` / `Ctrl+J` | New line in the task. |
+| `Ctrl+N` | While typing, choose the folder, model and thinking level first. |
+| `Ctrl+Z` | Put Pi in the background, and `fg` brings it back. Sessions keep running. Works in an attached session too. |
+| `Left` / `Right` | Attach to the selected session. |
+| `Left` twice | From an empty Pi prompt, put this session on the board and open it. |
+| `Up` / `Down` | Move between rows. |
+| `PgUp` / `PgDn` | Move by a screenful. |
+| `Home` / `End` | First or last row. |
+| `Alt+Up` / `Alt+Down` | Previous or next group. |
+| `Alt+1`..`Alt+9` | Attach to that row. |
+| `Space` | Open or close Peek. |
+| `/` | Pick one of Pi's commands. It closes the board and runs in the Pi you opened it from. A template or skill starts a session instead, like any task. |
+| `Ctrl+F` | Filter the list. |
+| `Ctrl+S` | Group by state or by directory. |
+| `Shift+Up` / `Shift+Down` | Move the row up or down its group. |
+| `Ctrl+G` | Write the task in `$VISUAL` or `$EDITOR`. |
+| `Ctrl+T` | Pin or unpin. |
+| `Ctrl+R` | Rename. |
+| `Ctrl+X` | Stop the session; press again within 2 seconds to delete it. |
+| `Ctrl+D` | Confirm marking an inactive session Done. |
+| `Ctrl+B` | Hold or unhold an inactive session. |
+| `Ctrl+A` | Select several rows. |
+| `Ctrl+O` | Read-only transcript. |
+| `Ctrl+E` | Evidence / Diagnostics. |
+| `Ctrl+K` | Delete inactive rows in the selected state. |
+| `!` | node-pty diagnostics and fix steps. |
+| `?` | Help. |
+| `Esc` | Clear a draft, or leave the board. |
+| `Ctrl+C` | Clear a draft; press twice within a second to quit Pi, from the board or an attached session. Background sessions keep running. |
+
+On macOS, the `Alt` keys need your terminal to send Option as Alt.
+
+
+## Multi-select
+
+Press `Ctrl+A` 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 |
+| --- | --- |
+| Any text | Start a reply, and press `Enter` to send it without attaching. |
+| `Left` / `Right` | Attach to the session. |
+| `Up` / `Down` | Move to the previous or next session. |
+| `Ctrl+O` | Open the read-only transcript. |
+| `Ctrl+E` | Open Evidence / Diagnostics. |
+| `Ctrl+D` | Confirm marking the inactive session Done. |
+| `Ctrl+B` | Hold or unhold the session. |
+| `!` | Open node-pty diagnostics and fix steps. |
+| `Space` / `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
+
+The 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 `Ctrl+F` 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. The 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.
+
+## Configuration
+
+Settings live in `~/.pi/agent/extensions/pi-board/config.json`. Everything is optional, and a missing or broken file means the defaults. Restart Pi after editing it.
+
+```json
+{
+  "model": "provider/model-id",
+  "autoDone": false
+}
+```
+
+### Helper model
+
+Titles, row summaries and telling `Needs answer` from `Needs instructions` can use a model. **It's off by default**, so the board makes no model calls of its own and uses built-in rules instead.
+
+Run `/board-model` inside Pi to pick a model or turn it off. It's saved to the file above and applies to sessions started from then on. These calls run through Pi, so any model Pi can use works, and they send up to 6,000 characters of a session's latest reply to that model.
+
+### Other settings
+
+| Key | Default | Purpose |
+| --- | --- | --- |
+| `model` | off | Helper model, as `provider/id`. |
+| `groupBy` | `state` | `state` or `directory`. `Ctrl+S` changes it. |
+| `root` | `~/.pi/agent/agent-board/` | Where the board stores its state. |
+| `titleThinking` | `low` | Thinking level for titles. |
+| `autoDone` | `false` | Let the helper model mark sessions Done. |
+| `codeRefs` | `true` | Issue and pull request badges. |
+| `disablePty` | `false` | Turn off live terminal sessions and attach. |
+| `attachMouse` | `true` | Mouse handling in attached sessions. |
+| `mouseScroll` | `true` | Mouse wheel scrolling in attached sessions. |
+| `wheelLines` | `1` | Lines per wheel notch, from 1 to 50. |
+| `maxWarmHosts` | `4` | Idle sessions kept ready for fast attach, from 0 to 50. |
+| `warmHostTtlMs` | `600000` | How long an idle one is kept; `0` keeps it. |
+| `nativePaste` | `true` | X11 PRIMARY copy and middle-click paste. |
+| `forwardClipboard` | `true` | Forward OSC 52 clipboard writes from attached sessions. |
+| `forwardImages` | `true` | Forward terminal images from attached sessions. |
+| `imeFix` | `true` | IME cursor fix in attached sessions. |
+| `terminalSnapshot` | `true` | Newer attach path; `false` uses the older one. |
+| `replyGuard` | `true` | Discard stray terminal replies delivered as input. |
+
+An `AGENT_BOARD_*` environment variable that's already set overrides the file for that run.
+
+Setting `terminalSnapshot` to `false` 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 the 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. The 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.
+
+

package/packages/board/package.json

@@ -0,0 +1,81 @@
+{
+  "name": "@huseynsnmz/pi-board",
+  "version": "0.18.2",
+  "description": "A board for Pi's background sessions: start, watch, reply to and attach to them. A fork of @zhuxixi/pi-agent-board.",
+  "type": "module",
+  "main": "./index.ts",
+  "exports": "./index.ts",
+  "files": [
+    "CHANGELOG.md",
+    "CONTRIBUTING.md",
+    "LICENSE",
+    "README.md",
+    "SECURITY.md",
+    "docs",
+    "index.ts",
+    "runner",
+    "src"
+  ],
+  "keywords": [
+    "pi-package",
+    "pi-extension",
+    "pi",
+    "pi-coding-agent",
+    "agent-board",
+    "background-agents",
+    "dashboard"
+  ],
+  "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/huseynsnmz/pi-suite.git",
+    "directory": "packages/board"
+  },
+  "publishConfig": {
+    "access": "public"
+  },
+  "engines": {
+    "node": ">=20"
+  },
+  "pi": {
+    "extensions": [
+      "./src/index.ts"
+    ]
+  },
+  "scripts": {
+    "typecheck": "tsc --noEmit",
+    "test": "node scripts/run-tests.mjs",
+    "test:perf": "node scripts/run-perf-gate.mjs",
+    "pack:dry": "npm pack --dry-run",
+    "verify": "npm run typecheck && npm run test:perf && npm test && npm run test:coverage && npm run pack:dry"
+  },
+  "peerDependencies": {
+    "@earendil-works/pi-coding-agent": "*",
+    "@earendil-works/pi-tui": "*"
+  },
+  "peerDependenciesMeta": {
+    "@earendil-works/pi-coding-agent": {
+      "optional": true
+    },
+    "@earendil-works/pi-tui": {
+      "optional": true
+    }
+  },
+  "devDependencies": {
+    "@earendil-works/pi-coding-agent": "1.5.0",
+    "@earendil-works/pi-tui": "1.5.0",
+    "@types/node": "26.6.6",
+    "typescript": "7.0.2"
+  },
+  "dependencies": {
+    "@xterm/headless": "6.0.0",
+    "node-pty": "1.1.0"
+  },
+  "overrides": {
+    "test-exclude": {
+      "glob": "14.0.3",
+      "minimatch": "11.0.4"
+    }
+  },
+  "private": true
+}

package/packages/board/runner/job-runner-legacy.mjs

@@ -0,0 +1,68 @@
+/**
+ * Pre-coordinator direct-write helpers for job-runner (issue #91, PR #2).
+ *
+ * The View State Coordinator is the single logical writer of state.json /
+ * status.json. The ONLY legitimate direct-write path left in the JSON runner
+ * is the explicit `AGENT_BOARD_COORDINATOR=off` escape hatch (a documented
+ * designed exception in the writer-boundary test): a user who switches the
+ * coordinator off keeps the exact pre-coordinator persistence semantics.
+ *
+ * This module exists so `runner/job-runner.mjs` itself never imports the
+ * state materializers — the boundary test allowlists THIS file (disabled
+ * escape hatch), not the runner.
+ */
+import { projectViewState } from "../src/core/events.mjs";
+import { readState, writeState, writeStatus } from "../src/core/store.mjs";
+
+/**
+ * Direct-write the run status and its projected view state (the boot +
+ * throttled-persist tail of the pre-coordinator persist, minus the evidence
+ * artifacts which stay runner-owned in both modes).
+ * @param {{ root: string, viewId: string, runId: string, status: object }} ctx
+ */
+export function legacyPersistState({ root, viewId, runId, status }) {
+	void runId;
+	writeStatus(root, status);
+	writeState(root, projectViewState(status, Date.now(), readState(root, viewId)));
+}
+
+/** @param {string} root @param {string} viewId @param {string} runId @param {object} status */
+export function legacyWriteStatus(root, viewId, runId, status) {
+	void viewId;
+	void runId;
+	writeStatus(root, status);
+}
+
+/** @param {string} root @param {string} viewId @param {object} state */
+export function legacyWriteState(root, viewId, state) {
+	void viewId;
+	writeState(root, state);
+}
+
+/**
+ * Direct-write the plan-ready row state ("Approve this plan?") — exact legacy
+ * parity with the pre-coordinator finalizeSteeringIfNeeded write.
+ * @param {string} root @param {string} viewId @param {string} runId
+ */
+export function legacyPlanReadyStateWrite(root, viewId, runId) {
+	const prev = readState(root, viewId);
+	if (!prev) return;
+	prev.semanticState = "needs_input";
+	prev.processState = "exited";
+	prev.needsInput = true;
+	prev.question = "Approve this plan?";
+	prev.summary = "Plan ready for approval";
+	prev.currentRunId = runId;
+	prev.updatedAt = Date.now();
+	writeState(root, prev);
+}
+
+/**
+ * Direct-write the queued follow-up's bootstrap status + projected state —
+ * exact legacy parity with drainQueuedFollowUp.
+ * @param {string} root @param {string} viewId @param {object} nextStatus
+ */
+export function legacyFollowupBootstrap(root, viewId, nextStatus) {
+	writeStatus(root, nextStatus);
+	writeState(root, projectViewState(nextStatus, Date.now(), readState(root, viewId)));
+}