@astralyn/pi 0.84.14 → 0.84.15

package/docs/bundled/extensions/background.md

@@ -91,8 +91,9 @@ Running and finished counts appear in the footer as `bg 2 running · 1 done`; ta
 
 - Background tasks inherit the session's `PI_*` environment variables (`PI_SESSION_ID`, `PI_MODEL`, …) just like the built-in bash tool, snapshotted when the task starts.
 - Tasks run through the session's configured shell (`shellPath`) and honor `shellCommandPrefix`, matching the built-in bash tool. The prefix is applied at execution time only — it never appears in task labels or notifications. Unlike the built-in bash tool, `bg` does not apply an SDK host's `spawnHook` — extensions have no access to it — so a host that rewrites or sandboxes commands through that hook does not cover background tasks.
-- Output streams directly to a system-temp file (`pi-bg-<id>.log`), never into the project or into memory. Memory holds only a byte counter.
+- Output streams directly to a system-temp file (`pi-bg-<id>.log`), never into the project or into memory. Memory holds only a byte counter. Task allocation creates the file exclusively and retries a new id on collisions, so a stale log is never overwritten.
 - Output is capped at 20MB. Hitting the cap kills the task and marks it `failed` rather than silently truncating.
+- The stall watchdog only reports `waiting for input` after it can read a stable prompt-like tail. A temporary tail-read error keeps the task running and eligible for later probes instead of producing a false stall; if the task finishes while its tail remains unreadable, the completion reports that read error.
 - At most 8 tasks may run concurrently; `create` reports the running tasks when the limit is reached.
 - Aborting the current turn (Esc) does not kill background tasks — that is what `kill` and `/bg` are for.
 - Session shutdown, `/reload`, new sessions, and session switches kill all running tasks; those kills are silent (no notification flood). There is no restart reattachment: finished-task records live only for the current session.

package/docs/bundled/extensions/deepwiki.md

@@ -7,9 +7,11 @@ It is intentionally not a general MCP bridge. The extension exposes one dedicate
 | Action | Behavior |
 |---|---|
 | `structure` | List the generated wiki topics for a repository. |
-| `contents` | Read the generated wiki — one page via `page` (recommended), or everything when `page` is omitted (truncated past ~120k chars). |
+| `contents` | Read the generated wiki — one page via `page` (recommended), or everything when `page` is omitted. |
 | `question` | Ask a focused question about a repository. |
 
+Every action has a hard model-facing limit of 120,000 characters. `contents` prefers page-aware cuts and reports omitted pages; `structure` and `question` use an action-specific truncation notice.
+
 ## Usage
 
 ### Parameters
@@ -17,7 +19,7 @@ It is intentionally not a general MCP bridge. The extension exposes one dedicate
 - `action`: `structure`, `contents`, or `question`
 - `repoName`: one `owner/repo` string for `structure` and `contents`; for `question`, one repo as a string, or 2–10 repos as an array (comma-separated string also accepted)
 - `question`: required only for `action: "question"`
-- `page`: optional, only for `action: "contents"` — 1-based index or page title from `structure` (plain titles such as `Extension System`, not numbered outline lines like `4.4 …`). Leading outline numbers on titles are stripped when matching. Unknown `page` fails with available titles listed.
+- `page`: optional, only for `action: "contents"` — a positive 1-based integer or page title from `structure` (plain titles such as `Extension System`, not numbered outline lines like `4.4 …`). Zero, negative, fractional, non-finite, and blank values are rejected. Leading outline numbers on titles are stripped when matching. Unknown `page` fails with available titles listed.
 
 `repoName` is normalized before validation (`owner/repo`, GitHub/DeepWiki URLs, JSON-array strings for multi-repo mistakes). `pageName`/`pageTitle` are accepted as `page` aliases. If `action` is omitted, defaults to `question` when a question is present, `contents` when `page` is present, else `structure`. Repositories not indexed on DeepWiki return repository-not-found errors — run `structure` first to detect that.
 
@@ -49,8 +51,8 @@ Avoid DeepWiki when the authoritative source is local or time-sensitive:
 ## Limits
 
 - A repository may not be indexed. DeepWiki can return that as normal text, so the extension treats repository-not-found messages as tool errors.
-- `contents` responses are truncated at a ~120k-character budget on `# Page:` boundaries (whole pages kept in order; at least the first page survives, cut mid-page if it alone exceeds the budget). A trailing notice reports shown/total pages, the full length, up to 20 omitted page titles, and points at `page` reads and `action: "question"` for the rest. Details carry `shownPages` / `truncatedChars` when this happens; `outputLength` always reflects the full untruncated response. Single-page reads set `requestedPage` / `pageIndex` instead and share the same budget.
-- Network requests time out after 45 seconds and surface as Pi tool errors.
+- All model-facing responses are capped at 120,000 characters. `contents` prefers `# Page:` boundaries (whole pages kept in order; at least the first page survives, cut mid-page if it alone exceeds the budget). Its trailing notice reports shown/total pages, the full length, up to 20 omitted page titles, and points at `page` reads and `action: "question"` for the rest. `structure` and `question` append a focused-request truncation notice. Details carry `shownPages` / `truncatedChars` when applicable; `outputLength` always reflects the full cached response. Single-page reads set `requestedPage` / `pageIndex` and share the same hard budget.
+- Each transport response is streamed with an 8 MiB byte limit before JSON/SSE parsing; oversized, failed, aborted, and timed-out responses never enter the cache. Network attempts time out after 45 seconds and surface as Pi tool errors.
 - Use local Pi tools (`read`, `grep`, `find`, `ls`) for workspace state. DeepWiki answers describe repository snapshots indexed by DeepWiki, not local uncommitted files.
 
 ## Implementation notes
@@ -59,4 +61,4 @@ DeepWiki's public MCP endpoint exposes exactly three operations: list a wiki's p
 
 DeepWiki may return generated explanations with source-file citations and "related pages" links. The TUI uses a local renderer (`render.ts`) rather than Pi's generic fallback, which would dump the full (often large) `content` text. Call questions, page names, and result titles are whitespace-normalized into bounded one-line summaries. Collapsed result text uses the quieter tool-output color and keeps the configured expand hint on the same logical line; expanding renders the complete response as Markdown. Historical malformed titles, requested pages, and error messages are bounded and fall back safely instead of breaking transcript rendering.
 
-Successful responses are cached in-process for 10 minutes, keyed by action, repo, and question. Failed, aborted, and timed-out requests are not cached. The cache stores the full response; `contents` truncation is recomputed per call, so cached and fresh calls return identical text.
+Successful responses are cached in-process for 10 minutes, keyed by action, repo, and question. Caller cancellation is checked before cache lookup as well as after transport, so an already-aborted call never receives a cached result. Failed, aborted, timed-out, and oversized requests are not cached. The cache stores the transport-bounded full response; `contents` page extraction and model-facing truncation are recomputed per call, so cached and fresh calls return identical text.

package/docs/bundled/extensions/question.md

@@ -4,7 +4,8 @@ Adds a `question` tool for asking one to four multiple-choice questions when the
 
 ## Behavior
 
-- Each option requires a concise description of its consequence or trade-off. Questions, labels, descriptions, and previews have input-length limits so the dialog stays usable.
+- Each option requires a concise description of its consequence or trade-off. Questions, headers, option labels, descriptions, and provided previews must contain visible non-whitespace text and stay within their input-length limits; punctuation such as a trailing question mark is guidance, not a validation requirement.
+- Question tool calls execute sequentially, so two calls in one tool batch cannot open competing blocking dialogs.
 - A single single-select question submits as soon as the user selects an option.
 - A multi-question flow advances after each single-select answer; multi-select uses `Space` to toggle choices and Enter to continue. Once every question is answered, a **Review answers** view requires explicit submission.
 - Options are numbered; pressing `1`–`9` jumps to the matching option — selecting it in single-select, toggling it in multi-select. The custom-answer row's number opens its input.
@@ -13,8 +14,9 @@ Adds a `question` tool for asking one to four multiple-choice questions when the
 - `Type something` is appended automatically for custom answers. Authored options may not use reserved labels (`Other`, `Type something`, the legacy `Type something.`, or `Chat about this`); the comparison is case-insensitive and ignores surrounding whitespace.
 - `Tab` opens a note editor for the focused option; in multi-select, the option must be selected first. In single-select it also selects the option, and cancelling the note editor with `Esc` restores the previous selection. On the custom-answer row, it opens custom-answer input.
 - Multi-select custom answers stay on the `Type something` row, are selected when saved, and can be toggled with `Space` without losing text. Enter on that row opens the input while no custom answer exists yet.
-- `preview` shows focused single-select content beside the choices on wide terminals and beneath them on narrow terminals. Preview height is capped and reports hidden lines. Previews on multi-select questions are rejected with a `preview_multiselect` error.
+- `preview` shows focused single-select content beside the focused choice on wide terminals and directly beneath it on narrow terminals. Preview height is capped and reports hidden lines. Previews on multi-select questions are rejected with a `preview_multiselect` error.
 - The dialog is available only in TUI mode. RPC, JSON, and print calls return a structured `no_ui` error rather than attempting a custom component.
+- Short terminals use a height-bounded vertical viewport. Moving option focus keeps that option and its preview visible; long Review answers can be scrolled with the configured up/down bindings while Enter still submits and Esc returns to editing.
 - Aborting the turn closes the dialog and resolves the call as cancelled with the answers given so far.
 
 ## Result contract
@@ -31,7 +33,7 @@ Adds a `question` tool for asking one to four multiple-choice questions when the
 }
 ```
 
-Only `content` reaches the model. Successful results are numbered, clearly identify single/custom/multi answers, retain notes, and state when a preview was selected without echoing its full source. Cancelling — via `Esc` or a turn abort — lists any answers already given as partial answers alongside the decline message. Model-facing output is capped at 12,000 characters; if it is truncated, the result instructs the model to ask a focused follow-up question. Notes and custom answers are capped at 4,000 characters in the dialog.
+Only `content` reaches the model. Successful results are numbered, clearly identify single/custom/multi answers, retain notes, and state when a preview was selected without echoing its full source. Cancelling — via `Esc` or a turn abort — lists any answers already given as partial answers alongside the decline message. Model-facing output is capped at 12,000 characters; if it is truncated, the result instructs the model to ask a focused follow-up question. Notes and custom answers are capped at 4,000 characters in the dialog. Only `outcome: "error"` is mapped to Pi's protocol-level tool error flag; answered, cancelled, and clarification outcomes remain normal results.
 
 The transcript uses a private `renderCall` / `renderResult` only to replace raw question JSON and model-oriented result text with concise user summaries. The collapsed call keeps a bounded header; expanding lists every question in full and marks multi-select prompts. Cancelled and clarification outcomes report `answered N of M`, and the expanded result preserves partial decisions and notes. Human-readable validation errors are shown instead of machine codes, while older or malformed session details fall back defensively to bounded content. Schema-level argument failures show only the first bounded error (plus any remaining count) when collapsed and reveal the bounded validator report with received arguments only when expanded. Pi retains its native tool shell and pending/error state.
 
@@ -48,5 +50,5 @@ Dialog footers use configured keybindings where Pi exposes them, format compact
 
 - Uses Pi's native `ctx.ui.custom()` lifecycle; no state is shared with another extension.
 - The render cache is keyed by terminal width **and height**, because preview height depends on available rows and Pi resize only requests a render. Preview markdown rendering is additionally memoized per text and dimensions so editor keystrokes don't re-parse previews.
-- `validateQuestions` enforces only what the JSON schema cannot express: case-insensitive uniqueness, reserved-label rejection, and the preview/multi-select conflict. Length and count limits are enforced against the schema before the tool executes.
+- `validateQuestions` defensively trims every visible text field and rejects whitespace-only content, then enforces case-insensitive uniqueness, reserved-label rejection, and the preview/multi-select conflict. The JSON schema separately carries non-empty, length, and count constraints before execution.
 - Dialog navigation follows Pi's injected select/input keybindings where applicable; compact footer labels show the first configured binding in a human-readable form. Custom actions such as Space-to-toggle remain explicit in the footer.

package/docs/bundled/extensions/router.md

@@ -108,7 +108,7 @@ There is **no migration** from any older models-manager config, and Pi updates d
 ## Limits
 
 - SSE only — no Codex WebSocket or zstd-compressed request body.
-- Catalog probe expects OpenAI-style `{ data: [{ id }] }` response format.
+- Catalog probe expects OpenAI-style `{ data: [{ id }] }` response format. Successful catalog bodies are streamed with a 4 MiB limit; oversized responses are cancelled, and non-OK response text is bounded before it is shown.
 - Empty model list → provider is not registered (nothing appears in `/model`).
 - Body is Codex-oriented for transparent gateways; auth and URL remain Platform Responses (`sk-` + `/responses`).
 - Replayed optional top-level `ResponseItem.id` identity fields are omitted from stateless requests, matching Codex CLI 0.145's default `store: false` wire behavior. Required semantic references such as `item_reference.id`, plus `call_id` and encrypted reasoning content, remain intact.

package/docs/bundled/extensions/statusline.md

@@ -40,6 +40,7 @@ CTX 2.1%/1.0M                    ↑13k ↓13k R440k CH99.4% $0.074
 - `↓` cumulative output tokens.
 - `R` cumulative cache-read tokens.
 - `W` cumulative cache-write tokens, omitted when zero.
+- Cumulative totals include assistant requests, usage-bearing tool results, compaction summaries, and branch summaries on the active branch.
 - `CH` cache-hit percentage for the latest assistant request, calculated as
   `cacheRead / (input + cacheRead + cacheWrite)` and shown only when that
   request used cache.

package/docs/bundled/extensions/subagent.md

@@ -39,7 +39,7 @@ There are exactly two profiles:
 - **Explorer** (`explorer`, default): read-only investigation with `read`, `grep`, `find`, `ls`, and `bash`. Bash remains available for Git history and inspection commands such as `git log`, `git diff`, `git blame`, `git show`, `git status`, `wc`, `head`, and `tail`. Its system prompt forbids redirects, heredoc writes, temporary files, state-changing Git commands, installs, and network access.
 - **General** (`general`): implementation, file changes, and stateful verification with `read`, `bash`, `edit`, and `write`.
 
-There are no user or project profile files. Child sessions load no extensions, skills, prompt templates, or themes, so workers cannot recursively call `subagent` or inherit unrelated extension capabilities. Explorer continues to skip project context files such as `AGENTS.md`; General loads trusted project context normally.
+There are no user or project profile files. Child sessions load no extensions, skills, prompt templates, or themes, so workers cannot recursively call `subagent` or inherit unrelated extension capabilities. Both profiles load the applicable repository instructions for their working directory, including layered `AGENTS.md` or `CLAUDE.md` files. Explorer's tool set and system prompt remain strictly read-only.
 
 Worker contexts are isolated, but workers share the parent's checkout. Concurrent tasks therefore must be independent and must not perform overlapping writes.
 
@@ -67,13 +67,13 @@ Overrides are saved atomically in:
 ~/.pi/agent/subagent.json
 ```
 
-Only `explorer` and `general` keys are valid. A stale or invalid `subagent.json` (older formats, unknown profiles, or malformed JSON) is reset to an empty, fully inheriting config the first time it is loaded, so an old file never blocks the tool or `/agents`. Overrides affect future workers and never change the parent session's model or thinking level.
+Only `explorer` and `general` keys are valid. A malformed, unsupported, unreadable, or future-version `subagent.json` is never rewritten during load: workers temporarily inherit the parent settings and the UI reports the problem. On the first actual settings change, Pi backs up the original bytes to a collision-safe `.invalid-<timestamp>-<pid>.bak` file before writing a valid replacement; if the backup fails, the save is cancelled. Concurrent Pi processes lock, re-read, and merge profile changes before an atomic write, and no-op changes leave the file and its timestamp untouched. Overrides affect future workers and never change the parent session's model or thinking level.
 
 ## Lifecycle and retry
 
 - The parent call waits until every worker reaches a terminal state.
 - Parent abort, `/reload`, `/new`, `/resume`, `/fork`, and session shutdown abort active and queued workers.
-- Provider auto-retry remains visible as `Retrying (n/m) in Xs`.
+- Provider auto-retry remains visible under the expanded task Outcome as `Retrying (n/m) in Xs`.
 - A retryable failure that produced no turns or tool use may be retried at task level up to two more times. Runs with partial work are never restarted.
 - Retry backoff does not hold a concurrency slot; another queued worker can run while the failed task waits.
 - A parent abort or session shutdown interrupts queued and retrying workers immediately.
@@ -82,56 +82,46 @@ Child sessions share the parent's canonical model/authentication runtime, so ext
 
 ## Transcript UI
 
-The native tool title owns whole-call elapsed time. While running, the collapsed view lists one width-bounded physical row per task:
+Pi's native tool chrome owns the aggregate `● Subagent` call marker and the dim continuation rail. The collapsed view is a compact flow containing one cell per task:
 
 ```text
-● Subagent · 12s
-│ › #1 Explorer · Thinking...
-│ › #2 Explorer · Run git log
-│ ○ #3 Explorer · Queued
-│ › #4 General · Compacting...
+● Subagent
+│ ✼ #1 Explorer · ○ #2 Explorer · ✓ #3 General · × #4 General
 ```
 
-`#N` is the task's stable one-based input position. Rows always remain in `#1` through `#N` order: there is no progress header, prompt excerpt, row cap, active-first reordering, or `+N more` truncation. A row reports the task's current state directly:
+`#N` is the task's stable one-based input position. Cells always remain in `#1` through `#N` order and contain only the task marker, ordinal, and profile. Running cells use the breathing dot-to-star bloom, queued cells use `○`, and completed, failed, or aborted cells use `✓`, `×`, or `■`. Wide batches wrap at cell boundaries with uniform columns. If the terminal is narrower than one complete cell, every task receives its own width-truncated row so all ordinals remain visible. Collapsed cards never expose prompts, activities, timings, token totals, costs, or failure text. Live repainting runs at 120ms only for visible collapsed blooms and at one second for expanded running durations or retry countdowns; queued, static, settled, and disposed rows keep no refresh timer.
 
-- `Starting...` before the worker has begun a turn;
-- `Thinking...` while the model is active without a tool;
-- `Read`, `Search`, `Find`, `List`, `Run`, `Edit`, or `Write` for the current tool;
-- `Compacting...` during worker auto-compaction;
-- `Queued` while waiting for a worker slot;
-- `Retrying (n/m) in Xs` during retry backoff;
-- `Completed`, `Failed`, or `Aborted`, with duration when the task started.
-
-Long states and activities are truncated by visible terminal width, including ANSI styling and wide CJK characters, instead of wrapping onto continuation rows.
-
-Once settled, aggregate cost joins the frozen duration in the native title, and the ordered task rows become the complete collapsed outcome summary:
+Expanding removes aggregate Batch chrome and gives every task the same four-part layout:
 
 ```text
-● Subagent · 1m 24s · $0.042
-│ ✓ #1 Explorer · Completed · 48s
-│ ✓ #2 Explorer · Completed · 1m 3s
-│ × #3 General · Failed · 36s
-│ ✓ #4 Explorer · Completed · 1m 20s
+● Subagent
+│ #1 Explorer · anthropic/claude-opus-5 · max · 99.9k tok · 60 tool calls · 12m 47s
+│
+│ Prompt
+│   Inspect the renderer and report the exact data flow.
+│
+│ Activity · last 3 of 60 tool calls
+│   Read(src/extensions/subagent/render.ts)
+│   Grep(src/extensions/subagent)
+│   Run(npm test -- test/subagent-render.test.ts)
+│
+│ Outcome
+│   Still running...
 ```
 
-Zero cost is omitted. There is no separate aggregate count line; the per-task markers show the mixed outcome directly.
+The single-line task header always shows the profile, exact `provider/model` ID, raw thinking level (including `off`), cumulative provider-reported token usage, tool-call count, and task duration. Tokens use compact `k`/`M` notation with at most one decimal. The header omits working directory, turns, per-run cost, and aggregate Batch timing or cost, and truncates rather than wraps when the terminal is narrow.
 
-Expanded sections also remain in input order. Their single-line header contains only identity and compact runtime metadata:
+Prompt contains the complete original task briefing and remains visible in every state. Prompt, Activity, and Outcome bodies use a two-column inset under their section labels.
 
-```text
-── #1 Explorer · anthropic/claude-sonnet-4-5 · medium · 3 tool uses · 2 turns · 1m 5s
+Activity retains only the latest three actual tool calls, in execution order. Its denominator is the run's total tool-call count; small histories use `Activity · N tool calls`, and an empty history says `No tool calls yet.` Calls use compact `Read(path)`, `Grep(path)`, `Find(pattern)`, `List(path)`, `Run(command)`, `Edit(path)`, or `Write(path)` presentation. Synthetic compaction entries do not increment or occupy the tool-call history.
 
-Prompt
-<complete original task briefing>
-
-Activity
-  Read .github/workflows/ci.yml
-› Run npm test
-```
+Outcome stays in the same position throughout the task lifecycle:
 
-The thinking level is shown as its raw value (`medium`, not `medium thinking`) and omitted when it is `off`; a non-parent working directory appears as `cwd: ...`. Per-run token, context, and cost fields are omitted from this header.
+- queued or running: `Still running...`, followed by a retry countdown or active compaction state when applicable;
+- completed: the worker's final Markdown report, or `No outcome returned.`;
+- failed or aborted: the terminal reason, followed by `Partial outcome:` and the bounded report when useful output survived.
 
-Every expanded task shows the complete original Prompt, including while the batch is still running. Active and queued tasks show bounded Activity history and retry state. A completed, failed, or aborted task immediately switches to Error/Report presentation even if sibling tasks are still active; failed or aborted workers with useful output use `Report · partial`. Streaming assistant text is not copied into the parent transcript.
+A terminal task exposes its Outcome immediately even while sibling tasks remain active. Profile identity, section headings, activity states, and outcomes use semantic theme colors; report Markdown keeps its normal Markdown palette instead of inheriting a blanket success or error color.
 
 Full child transcripts are not stored separately. Activity, errors, reports, usage, and model-facing output remain bounded, and completed calls restore through the parent session tree.
 

package/docs/bundled/extensions/web-search.md

@@ -19,7 +19,7 @@ The MiniMax CN account (`minimax-cn`) is preferred over the global one (`minimax
 
 Configure with `/login minimax-cn` or `/login deepseek`, or by exporting the environment variables above.
 
-When no key is configured, `web_search` is removed from the model's tool set and system prompt entirely — the model never sees or calls it. This is re-evaluated on every session start (`startup`, `/new`, `/reload`, resume, fork), so a mid-session `/login` takes effect from the next session onward. The tool stays registered: it remains listed in `/tools` (where it can be force-enabled, in which case calls fail with the disabled message), and historical sessions render normally.
+When no key is configured, `web_search` is removed from the model's tool set and system prompt entirely — the model never sees or calls it. This is re-evaluated on every session start (`startup`, `/new`, `/reload`, resume, fork). When credentials are available, the extension leaves the host's active-tool set unchanged: normal registration keeps the tool available by default, while an explicit `/tools` or SDK-host disable remains respected until that host enables it again. The tool always stays registered for `/tools` and historical rendering; force-enabling it without keys returns the disabled message.
 
 ## Usage
 
@@ -34,9 +34,9 @@ The model-facing payload is Markdown containing up to 12 HTTP(S) source results.
 ## Limits
 
 - With no configured key the tool is hidden from the model (see Credentials); the disabled message only appears when the tool was force-enabled via `/tools` without keys.
-- Engine failures are independent: if one engine errors, the other's results are still returned; the tool errors only when every configured engine fails.
+- Engine failures are independent: if one engine errors, the other's results are still returned; the tool errors only when every configured engine fails. Error outcomes are marked as protocol-level tool errors; the credential-disabled warning is not.
 - MiniMax search uses the Coding Plan Search endpoint (`POST /v1/coding_plan/search`), which requires a Coding Plan key — a standard MiniMax API key may be rejected upstream.
-- DeepSeek search goes through the Anthropic-compatible endpoint (`/anthropic/v1/messages`, model `claude-sonnet-search`) with the server-side `web_search_20250305` tool; the request uses `max_tokens: 1024`, followed by the local output bound above.
+- DeepSeek search goes through the Anthropic-compatible endpoint (`/anthropic/v1/messages`, model `claude-sonnet-search`) with the server-side `web_search_20250305` tool; the request uses `max_tokens: 1024`, followed by the local output bound above. A response must contain a structured `web_search_tool_result`: an empty result array is a valid zero-result search, while text-only, malformed, or structured-error responses count as a provider failure and their synthesis is discarded.
 - Requests time out after 60 seconds (MiniMax) or 90 seconds (DeepSeek) and surface as Pi tool errors. Successful upstream response bodies are limited to 2 MiB, error bodies to 200 bytes, and model-facing error messages to 500 characters.
 
 ## Implementation notes

package/docs/development.md

@@ -6,8 +6,9 @@ This repository is the standalone distribution of `@astralyn/pi`. It publishes o
 
 - Node.js `>=22.19`
 - npm
+- `fd` (or `fdfind`) and `rg` for the complete test suite; Pi-managed copies are reused when available
 
-The package consumes the published `@earendil-works/pi-ai`, `@earendil-works/pi-agent-core`, and `@earendil-works/pi-tui` dependencies. It does not recreate the upstream monorepo or vendor those packages.
+The package consumes the published `@earendil-works/pi-ai`, `@earendil-works/pi-agent-core`, `@earendil-works/pi-client`, `@earendil-works/pi-protocol`, and `@earendil-works/pi-tui` dependencies. It does not recreate the upstream monorepo or vendor those packages.
 
 ## Install and run
 
@@ -59,12 +60,16 @@ Run all tests in an isolated home and configuration directory:
 npm run test:isolated
 ```
 
-Validate the exact upstream release baseline and local deviations:
+The runner keeps credentials and settings isolated, prepends the real Pi managed-bin when present, and preflights `fd`/`fdfind` plus `rg` before starting Vitest.
+
+Validate the exact upstream release baseline, all five upstream runtime dependencies, and local deviations:
 
 ```bash
 npm run diff:upstream -- --check
 ```
 
+Ordinary CI fetches the recorded release tag and runs this gate before build and tests.
+
 For interactive changes, also test in a real TTY, including pending and settled tool output, collapsed and expanded states, and relevant `/reload` or `/tree` flows.
 
 ## Repository layout

package/docs/extensions.md

@@ -2294,7 +2294,7 @@ By default, tool output is wrapped in Pi's native call/result shell, which owns
 
 Set `renderShell: "self"` when the tool should render its own shell instead of using the native shell. This is useful for tools that need complete control over framing or background behavior, for example large previews that must stay visually stable after the tool settles.
 
-For live progress UI (elapsed time, retry countdowns), schedule repaints from the renderer itself: store a timer handle in `context.state`, arm a `setTimeout` that calls `context.invalidate()` while `options.isPartial` is true, and clear it on the first settled render. `context.invalidate()` is a no-op after the row is disposed, so a trailing timeout is harmless.
+For live progress UI (elapsed time, retry countdowns), schedule repaints from the renderer itself: store a timer handle in `context.state`, arm a `setTimeout` that calls `context.invalidate()` only while the current view contains changing text, and clear it on the first static or settled render. Set `context.state.dispose` to the same idempotent cleanup function when a timer may still be armed; the shell invokes it when the row is disposed.
 
 Derive displayed time from an absolute timestamp or deadline (`Date.now()`), not by decrementing a counter on every refresh. A refresh is only a repaint opportunity; event-loop stalls and machine sleep must not extend a wall-clock timeout.
 
@@ -2316,7 +2316,7 @@ pi.registerTool({
 
 `renderCall` and `renderResult` each receive a `context` object with:
 - `args` - the current tool call arguments
-- `state` - shared row-local state across `renderCall` and `renderResult`
+- `state` - shared row-local state across `renderCall` and `renderResult`; an optional `dispose()` cleanup is called when the row is disposed
 - `lastComponent` - the previously returned component for that slot, if any
 - `invalidate()` - request a rerender of this tool row
 - `toolCallId`, `cwd`, `executionStarted`, `argsComplete`, `isPartial`, `expanded`, `showImages`, `isError`

package/npm-shrinkwrap.json

@@ -1,12 +1,12 @@
 {
 	"name": "@astralyn/pi",
-	"version": "0.84.14",
+	"version": "0.84.15",
 	"lockfileVersion": 3,
 	"requires": true,
 	"packages": {
 		"": {
 			"name": "@astralyn/pi",
-			"version": "0.84.14",
+			"version": "0.84.15",
 			"license": "MIT",
 			"dependencies": {
 				"@earendil-works/pi-agent-core": "0.84.4",

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@astralyn/pi",
-	"version": "0.84.14",
+	"version": "0.84.15",
 	"description": "Coding agent CLI with read, bash, edit, write tools and session management",
 	"type": "module",
 	"piConfig": {