@astralyn/pi 1.4.8 → 1.4.10

package/CHANGELOG.md

@@ -4,6 +4,74 @@ This file records `@astralyn/pi` releases beginning with the first Fork-owned re
 
 ## [Unreleased]
 
+## [1.4.10] - 2026-11-01
+
+### Added
+
+- `AgentSession.waitForQuiescence(signal?)`, `AgentSession.isQuiescent` and a `session_quiescent` session event report when no run, compaction, retry, unsettled background task or pending completion turn remains. Failed deliveries do not count, so the wait cannot deadlock on them.
+- RPC: `get_state` reports `isQuiescent`, and `RpcClient.waitForQuiescence()` and `collectEventsUntilQuiescent()` wait for background completion turns that `waitForIdle()` and `collectEvents()` miss.
+- `AgentSession.acknowledgeTaskDelivery(id)` tells the session that a direct SDK waiter consumed a background result, so the model is not notified about it again.
+- Background outcomes of `TasksContext.execute()` carry `reason: "submitted" | "detached"`, so executors no longer re-derive how their caller was released.
+- `TaskExecution.present` and `ctx.tasks.presentOutput(id, width, theme)` let an executor render its running task's Output in `/tasks` with its own styling. The presenter lives in memory with the running execution: it is never persisted, absent from snapshots and dropped at settlement, and a throwing presenter falls back to the default view.
+- A saved session owns an artifacts directory beside its file (`<name>/` for `<name>.jsonl`). `SessionManager.getArtifactDir()`, also on `ctx.sessionManager`, returns it, or `undefined` for a session that is not persisted. `SessionManager.createAt(path, cwd, options?)` creates a persisted session at an exact path.
+- In a saved session, each Agent keeps its complete report (`report.md`) and its child transcript (`transcript.jsonl`, a Pi session file linked to the main session through `parentSession`) in `<session>/agents/<task-id>/`. The `Full output:` path of an oversized report now stays valid after `pi -c` and Tasks retention. Details of a settled Agent show `Tool calls`, `Edited` (files changed through `edit` and `write`), `Report` and `Transcript`, and the report returned to the model ends with `Edited (edit/write): …` when the Agent changed files.
+
+### Changed
+
+- Print mode and `--mode json` wait for background tasks and the turns that deliver their results before printing the final response and exiting, instead of ending the process (and killing the work) after the prompt's own turn. A stderr line names the tasks being waited for. Ctrl+C (`SIGINT`) now cleans up like `SIGTERM` and exits 130; a second signal exits immediately.
+- `/tasks` panel:
+  - On wide terminals the list takes 40% of the width (34–60 columns). Pane titles and the reading or scroll state live in the borders.
+  - The inspector opens with the selected task's full title in bold and a `Label · Status · Mode · runtime` line, separated from the content by a rule.
+  - Details starts at the task ID instead of repeating source and status, and long values wrap within their column.
+  - Output shows an executor's human-readable display in place of its model-facing result when it has one.
+  - A settled report opens at its first line instead of its end, keeps the position you scroll to, and shows its scroll range in the bottom border when it overflows.
+  - Only a log streams from its file. A report always shows what its executor published, so an oversized Agent report renders as Markdown from its beginning instead of as a tail preview, and Details labels its saved file `Full report`.
+- `/tasks` in a narrow terminal: Escape returns from the inspector to the list and closes the panel only from the list. The footer names the action (`Esc back` or `Esc close`) and drops its lowest-priority hints first.
+- `/tasks` notices appear only when an action did not do what was asked, as a toned warning (`!`) or error (`×`) that clears on the next input or after about four seconds. Successful stop and background requests no longer show a message, and a pending stop confirmation marks its target row with `stop?`.
+- Agent in `/tasks` and the Transcript:
+  - A finished Agent's Output shows only its final report, whatever its outcome; its tool calls no longer follow the report.
+  - While an Agent runs, Output is a compact list of its tool calls with no heading: one `glyph tool target · duration` row per call with the tool names aligned (up to 8 characters), a `… N earlier tool calls` line for calls no longer retained, and one line holding the first line of a failed call's error. The expanded Transcript row uses the same columns.
+  - Paths inside the Agent's working directory appear relative, with forward slashes; paths outside it stay absolute.
+  - Tool-call durations read `42ms`, `6.2s`, then `1m 5s`.
+  - A running Agent's tool calls are styled in `/tasks` Output as in the Transcript's expanded row (status-colored glyph, tool name, muted target, dim duration, error line), fitted to the pane width, with the running call's elapsed time. Both views share one renderer, so the Transcript's expanded row now also shows a failed call's error line.
+  - Tool-call glyphs are the task status markers used elsewhere in `/tasks`: `×` for a failed call and `○` for a cancelled one instead of `✗` and `⊘`, and a running call shows the animated running-task spinner in the accent color instead of a dim `…`, which was also easy to confuse with the earlier-calls line. The plain fallback shows `›` for a running call.
+  - Styled rows right-align durations in one column that ends at the longest row, so short and clipped targets no longer leave their durations at different positions.
+- Background-task guidance tells the model to end its turn instead of waiting, because a finished task starts a new turn for it automatically. Agent guidance reserves `background: true` for when there is independent work to do meanwhile and points to the foreground otherwise. Agent and shell handoffs, the post-compaction reminder and the `tasks` prompt snippet no longer suggest `tasks wait`, `tasks` reserves `wait` for when the user asks to block on a task, and an expired wait, including one on a single task, says not to wait again. The default `tasks wait` window grows from 20 seconds to 4 minutes, the longest that keeps the next request inside a five-minute prompt cache; a wait still returns as soon as its task finishes.
+- Background completion cards no longer end with "Preview of the saved result.", and a failed shell task's card and model notification state its error once instead of repeating it at the end of the output.
+- Deleting a session from `/resume` also removes its artifacts directory and its `.tasks-late.jsonl` sidecar, which were previously left behind. The `trash` CLI receives every path in one call. Files that could not be removed are reported.
+- `/tasks` Details no longer repeats a path when a Details row already names the saved output file.
+- Concurrency lanes are namespaced by executor kind, so two executors can no longer share a lane by choosing the same key.
+- **Breaking:** background work, submitted or detached, is admitted only while the `tasks` tool is active, because the model could otherwise start work it cannot read, wait for or stop. When `builtin:tasks` is disabled or the tool is deactivated, `background: true` and every detach path are rejected without starting anything; work admitted earlier keeps running and delivering.
+- **Breaking (extension and SDK API):** a task's `mode` is `background` only once its caller has been released with a background outcome. A detach requested while the executor is still preparing waits for its acceptance, and a task answered inline stays `foreground` everywhere: `tasks list`, the statusline count, the `waitAny` cohort and saved records.
+- **Breaking (extension and SDK API):** a terminal task snapshot's `display` comes only from its completion; the last progress display no longer survives settlement. In `/tasks`, `display` replaces the result as the human view instead of being appended to it.
+- **Breaking (extension and SDK API):** `ctx.tasks.read()`, `tasks read`, and settled `tasks wait` and `waitAny` calls without `mode` read a report (`output: "report"`, such as an Agent's) from its start instead of its end, as its foreground result and completion notification already do. Logs, such as a shell command's output, still read from their end. An explicit `mode` selects the direction; `sinceBytes` anchors it, with `head` continuing forward from the offset and `tail` keeping the newest unread window.
+
+### Removed
+
+- **Breaking (SDK):** `session.tasks.markDelivered()` and the other delivery-ledger methods of `TaskRuntime` (`pendingNotifications()`, `claimNotification()`, `releaseNotification()`, `holdDelivery()`) are removed, along with `TaskDeliveryLedger`. Completion delivery is owned by the session; use `session.acknowledgeTaskDelivery(id)` after consuming a result directly.
+
+### Fixed
+
+- A standalone `TaskRuntime` with background enabled no longer keeps every settled background record forever and then rejects all background work once its retention limit is reached.
+- A task moved to the background while its executor was still preparing, and then answered inline, is no longer reported and saved as a background task.
+- Following a report's returned `next sinceBytes` now reads the next forward window instead of skipping to its tail. Continuation offsets use raw source bytes even when output is not valid UTF-8, and expanded `tasks read`/`wait` Transcript rows preserve the same end of the result that was read.
+- Timed-out, interrupted and closed task waits release their runtime subscriptions instead of retaining one Promise reaction per observation until settlement.
+- `/tasks` no longer polls a log that has no attached output file only to discard the published result it reads; the retention-limit error now names task pins and delivery leases instead of removed runtime claims.
+
+## [1.4.9] - 2026-10-31
+
+### Added
+
+- Fullscreen mode now pins a one-line summary of the nearest user message above the viewport at the top of the transcript, on the user message background. Click the summary to scroll back to the original message; regular mode is unchanged.
+
+### Changed
+
+- User messages no longer have a blank background row above and below the text, and start with a `❯` marker; wrapped lines align under the first text column. In fullscreen mode the pinned summary takes over the message's first row in place as it scrolls out of view, with `↑` in the marker's column.
+
+### Fixed
+
+- On Windows, `read`, `write`, `edit`, `ls`, `grep`, and `find` now resolve paths under the bash mount table, such as `/tmp/...` and `/usr/...`, to the directories bash uses instead of the current drive root. The bundled [Shell paths](docs/bundled/extensions/shell-paths.md) extension reads the mounts from the configured shell.
+
 ## [1.4.8] - 2026-10-31
 
 ### Removed