@astralyn/pi 0.82.3 → 0.82.5

package/docs/bundled/extensions/subagent.md

@@ -8,7 +8,8 @@ Exactly one mode is required per call:
 
 - **Single**: `agent`, `description`, and `prompt`.
 - **Parallel**: `tasks`, an array of independent task objects.
-- **Chain**: `chain`, an array of sequential task objects. `{previous}` in a later prompt is replaced by the previous worker's bounded final response.
+
+There is deliberately no chain mode: sequential work is driven by the parent, which reads each report before writing the next briefing.
 
 Every task object has:
 
@@ -17,11 +18,9 @@ agent?       Agent profile name; defaults to general
 description  Short UI label
 prompt       Self-contained worker briefing
 cwd?         Relative directory inside the parent working directory
-model?       Temporary provider/model override
-thinking?    Temporary thinking-level override
 ```
 
-Parallel and chain batches allow at most eight tasks. A session-scoped gate runs at most three workers concurrently, including sibling `subagent` calls from the same parent session.
+Parallel batches allow at most eight tasks. A session-scoped gate runs at most five workers concurrently, including sibling `subagent` calls from the same parent session.
 
 ## Agent profiles
 
@@ -50,26 +49,26 @@ Project definitions are loaded only after Pi trusts the project. Invalid Markdow
 
 Built-in profiles:
 
-- `general`: read, bash, edit, write, grep, find, and ls.
-- `explorer`: read-only `read`, `grep`, `find`, and `ls`, with low thinking by default.
+- `general`: read, bash, edit, and write.
+- `explorer`: `read`, `grep`, `find`, and `ls`, plus `bash` constrained by its system prompt to read-only inspection (git history, counting, and similar).
 
-A profile may only allow Pi built-in tools. Child sessions load no extensions, skills, or prompt templates, so a worker cannot recursively call `subagent` or inherit unrelated extension capabilities. Project context files such as `AGENTS.md` remain available.
+A profile may only allow Pi built-in tools. Child sessions load no extensions, skills, or prompt templates, so a worker cannot recursively call `subagent` or inherit unrelated extension capabilities. Project context files such as `AGENTS.md` remain available, except for the built-in `explorer`, which skips them: read-only exploration needs no commit/PR rules, and the parent interprets its results.
 
 ## Model and thinking selection
 
-The model/thinking resolution order is:
+The model/thinking resolution has exactly two layers:
 
 ```text
-per-call tool fields
-  > saved /agents profile override
-  > profile Markdown frontmatter
-  > current parent session
+saved /agents profile override > current parent session
 ```
 
+Callers cannot pick models per call, and profile Markdown `model`/`thinking`
+frontmatter is intentionally ignored: agent files travel across machines, so a
+pinned model rarely exists in the reader's environment.
+
 Run `/agents` to choose a profile and set either field to:
 
-- **inherit**: force the active parent-session value;
-- **agent default**: clear the saved override and use Markdown/default inheritance;
+- **inherit**: follow the parent session's current value;
 - a configured `provider/model` or explicit supported thinking level.
 
 Overrides are user-owned and saved atomically in:
@@ -84,8 +83,9 @@ They apply only to future subagent runs and never change the parent session's `/
 
 - The parent tool call waits until every worker reaches a terminal state.
 - Parent abort, `/reload`, `/new`, `/resume`, `/fork`, and session shutdown abort active child sessions. Queued workers do not survive the call.
-- Parallel worker failures do not cancel other independent workers. A failed or aborted chain step skips its remaining steps.
-- Progress is rendered in Pi's native tool transcript. The collapsed view shows status, recent activity, usage, and the configured expand hint; `Ctrl+O` shows bounded activities and final Markdown reports.
+- Parallel worker failures do not cancel other independent workers.
+- Transient provider errors auto-retry: the worker session retries retryable stream errors with backoff (visible as `Retrying (n/m) in Xs…`), and a failure that produced no work (for example a preflight auth throw) is rerun at the task level up to two more times. Runs with partial work behind them are never rerun.
+- Progress is rendered in Pi's native tool transcript. The collapsed view shows an intent line (for example `Verifying changes`), the current tool marked with `›`, live elapsed time, usage with a `ctx:` context watermark, and the configured expand hint. The call-level status dot belongs to the tool shell; run and activity rows only use `›`, `○`, `✓`, `×`, and `■`. `Ctrl+O` shows bounded activities and final Markdown reports; expanded batches start with a numbered contents list whose numbers match the `──` section headers.
 - Full child transcripts are not stored separately. Bounded run details remain in the parent tool result, so completed calls restore naturally in the parent session tree.
 - Nested usage is returned with the tool result and included in parent session accounting.
 

package/docs/bundled/extensions/todo.md

@@ -4,10 +4,12 @@ Adds a `todo` tool plus `/todos` for multi-step work, with a live overlay above
 
 ## Behavior
 
-- Actions: `create`, `update`, `list`, `get`, `delete`, `clear`. Statuses: `pending`, `in_progress`, `completed`, `deleted`. `list` accepts an optional `status` filter and `includeDeleted`; `status: "deleted"` includes tombstones directly.
+- Actions: `create`, `update`, `list`, `get`, `delete`, `clear`. Statuses: `pending`, `in_progress`, `completed`, `deleted`. `list` accepts an optional `status` filter and `includeDeleted`; `status: "deleted"` includes tombstones directly. Parameters that do not apply to the chosen action are rejected with guidance (for example `blockedBy` on `update` points at `addBlockedBy`/`removeBlockedBy`) instead of being silently ignored.
 - The live overlay renders above the editor and hides itself when there are no visible tasks.
-- Creation always starts a task as `pending`; `blockedBy` dependencies are supported for sequencing, and missing dependencies, deleted dependencies, self-dependencies, and cycles are rejected. A task cannot move to `in_progress` or `completed` until every `blockedBy` dependency is `completed`.
-- Deletion — via `delete` or `update` with `status: "deleted"` — leaves an immutable tombstone for branch history, removes that task from every dependent `blockedBy` list, and therefore releases dependents. `clear` empties the list without reusing ids.
+- Creation always starts a task as `pending` and requires both `subject` and `description` (what done means); `blockedBy` dependencies are supported for sequencing, and missing dependencies, deleted dependencies, self-dependencies, and cycles are rejected. A task cannot move to `in_progress` or `completed` until every `blockedBy` dependency is `completed` (a task that is already active may still take on a new incomplete dependency — a prerequisite discovered mid-work).
+- `update` manages both edge directions: `addBlockedBy`/`removeBlockedBy` change what the task waits on, `addBlocks`/`removeBlocks` change what waits on it (stored as the targets' `blockedBy`, with the same validation and cycle checks). An empty string removes `description`, `activeForm`, or `owner`; `metadata` merges with `null` deleting keys.
+- `list` lines show only unresolved blockers plus the task's `@owner`; full `blockedBy`/`blocks` detail lives in `get`.
+- Deletion — via `delete` or `update` with `status: "deleted"` — leaves an immutable tombstone for branch history, removes that task from every dependent `blockedBy` list, and therefore releases dependents; the tool result names pending dependents that ended up fully unblocked. A deletion cannot be combined with other field edits in the same call. `clear` empties the list without reusing ids.
 - Newly completed tasks remain visible for 30 seconds, then drop from the overlay; historical completions loaded by `/reload` or `/tree` stay hidden so live work remains prominent.
 - **Exactly one `in_progress`.** Moving a task to `in_progress` auto-demotes any other `in_progress` tasks to `pending`; the tool result lists demoted ids so the model sees the side effect.
 - **Verification soft nudge.** When a completion leaves the list fully done with 3+ completed tasks and no subject/description matching `verif|test|check|review`, the tool result appends a short NOTE (text only — `details` schema unchanged).

package/docs/compaction.md

@@ -284,7 +284,7 @@ Fired before auto-compaction or `/compact`. Can cancel or provide custom summary
 
 ```typescript
 pi.on("session_before_compact", async (event, ctx) => {
-  const { preparation, branchEntries, customInstructions, reason, willRetry, signal } = event;
+  const { preparation, branchEntries, customInstructions, reason, timing, willRetry, signal } = event;
 
   // preparation.messagesToSummarize - messages to summarize
   // preparation.turnPrefixMessages - split turn prefix (if isSplitTurn)
@@ -296,10 +296,14 @@ pi.on("session_before_compact", async (event, ctx) => {
 
   // branchEntries - all entries on current branch (for custom state)
   // reason - "manual" (/compact), "threshold", or "overflow"
+  // timing - "manual", "midTurn" (between tool batches), "postRun", or "prePrompt"
   // willRetry - whether overflow recovery intends to retry if compaction produces a safe retained context
   // signal - AbortSignal (pass to LLM calls)
 
-  // Cancel:
+  // Cancel. Consequences depend on timing: a "midTurn" cancel skips compaction
+  // for the rest of the run and the run continues at your risk of overflowing;
+  // other timings leave the over-threshold context to fail closed before the
+  // next provider request.
   return { cancel: true };
 
   // Custom summary:

package/docs/docs.json

@@ -64,6 +64,10 @@
           "title": "DeepWiki",
           "path": "bundled/extensions/deepwiki.md"
         },
+        {
+          "title": "Plan",
+          "path": "bundled/extensions/plan.md"
+        },
         {
           "title": "Question",
           "path": "bundled/extensions/question.md"

package/docs/extensions.md

@@ -454,12 +454,14 @@ Fired on compaction. See [compaction.md](compaction.md) for details.
 
 ```typescript
 pi.on("session_before_compact", async (event, ctx) => {
-  const { preparation, branchEntries, customInstructions, reason, willRetry, signal } = event;
+  const { preparation, branchEntries, customInstructions, reason, timing, willRetry, signal } = event;
 
   // reason - "manual" (/compact), "threshold", or "overflow"
+  // timing - "manual", "midTurn" (between tool batches), "postRun", or "prePrompt"
   // willRetry - whether overflow recovery intends to retry if compaction produces a safe retained context
 
-  // Cancel:
+  // Cancel. A "midTurn" cancel skips compaction for the rest of the run and the
+  // run continues at your risk; other timings fail closed on the oversized context.
   return { cancel: true };
 
   // Custom summary:

package/npm-shrinkwrap.json

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

package/package.json

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