@emiliosp/pi-maestro 0.17.0 → 0.18.1

package/ADR.md

@@ -246,7 +246,7 @@ failures during delegation still use the existing `run` failure path. Workflow r
 ### Evidence
 
 [Configuration](docs/configuration.md#model-access), [activation checks](src/maestro/checks/assertEnvironment.ts), and
-[delegation](src/tools/utils/pi-subagent-delegation.ts).
+[delegation](https://github.com/emilioSp/pi-maestro/blob/9d020b9177e93333736ade265db5e332fbb2a291/src/tools/utils/pi-subagent-delegation.ts).
 
 ## ADR-009: Select optional phases in the transition table
 
@@ -280,7 +280,7 @@ Approval can finish at `candidate-ready` without agent execution. Agent and mode
 
 ### Status
 
-Design decisions confirmed by the `owner`. Not implemented.
+Design decisions confirmed by the `owner`. Implemented.
 
 ### Context
 
@@ -399,6 +399,8 @@ execution-error policy: stop and report, retain files, and leave follow-up to th
 interruption through `session.abort()` followed by session cleanup, without a final model turn or synthetic `handoff`, and placed saved child sessions in `subagents/`
 beneath Pi's project session directory, not inside the repository. The `owner` chose Pi 1.5.0 as the minimum supported version, without fallbacks for earlier hosts. The
 `owner` explicitly excluded compatibility handling for external integrations from scope; no custom checks, adapters, or reduced-capacity fallback system are required.
-Existing boundaries are described in [subagent integration](docs/subagent-integration.md), [delegation](src/tools/utils/pi-subagent-delegation.ts),
-[builder execution](src/tools/main/run-builder.ts), and the [child extension](extensions/maestro-subagent.ts). These links describe the current implementation, not the
-planned SDK replacement.
+Existing boundaries are described in [subagent integration](docs/subagent-integration.md),
+[delegation](https://github.com/emilioSp/pi-maestro/blob/9d020b9177e93333736ade265db5e332fbb2a291/src/tools/utils/pi-subagent-delegation.ts),
+[builder execution](src/tools/main/run-builder.ts), and the
+[child extension](https://github.com/emilioSp/pi-maestro/blob/9d020b9177e93333736ade265db5e332fbb2a291/extensions/maestro-subagent.ts). These links describe the current
+implementation, not the planned SDK replacement.

package/CHANGELOG.md

@@ -3,6 +3,18 @@
 This file summarizes meaningful changes to the codebase, including behavior, data formats, architecture, and development tools. Git tags identify version boundaries;
 GitHub Releases are not required.
 
+## 0.18.1
+
+1. Running `builder`, `verifier`, and `simplifier` tools now show elapsed time, active tools, and streaming normal assistant text. Elapsed time keeps updating during
+   silent work. Pi controls preview and expansion, while intermediate activity stays out of the main model's context.
+
+## 0.18.0
+
+1. `Builder`, `verifier`, and `simplifier` now run in fresh native Pi SDK sessions. Activation no longer requires a separate agent extension. The `owner` can interrupt
+   them through Pi's cancel action.
+2. `Maestro` displays saved child session paths on completion or failure, for direct inspection or HTML export with Pi.
+3. `Maestro` no longer requires the `pi-subagents` package. Installation, activation, and agent `runs` use Pi alone.
+
 ## 0.17.0
 
 1. Added a standalone internal Pi SDK executor. Each invocation starts a fresh conversation with supplied model, thinking level, role guidance, working directory, and

package/README.md

@@ -84,16 +84,14 @@ An `escalation` asks the `owner` to decide an implementation question. A `findin
 1. macOS.
 2. Node.js 26 or later.
 3. Pi 1.5.0 or later.
-4. `pi-subagents` installed and enabled in Pi when `builder` is enabled.
-5. Access to the models for enabled agents.
-6. A project directory that Pi trusts.
+4. Access to the models for enabled agents.
+5. A project directory that Pi trusts.
 
 ## Installation
 
-The `owner` installs `pi-subagents` and `Maestro` with these commands:
+The `owner` installs `Maestro`:
 
 ```bash
-pi install npm:pi-subagents
 pi install npm:@emiliosp/pi-maestro
 ```
 
@@ -112,7 +110,7 @@ Activate `Maestro`:
 /maestro
 ```
 
-During activation, `Maestro` checks project trust, configuration, and enabled agent and model availability. With `builder` disabled, only project trust and configuration
+During activation, `Maestro` checks project trust, configuration, and model availability for enabled agents. With `builder` disabled, only project trust and configuration
 are checked. Model availability comes from Pi's model registry. If a check fails, `Maestro` stays disabled and reports the problem.
 
 The `owner` follows this workflow:
@@ -124,8 +122,14 @@ The `owner` follows this workflow:
 5. Reviews `verifier` `findings` and chooses an action for every `finding`.
 6. Reads Maestro's summary at `candidate-ready` and performs the final review.
 
-`Maestro` starts the `verifier`, when enabled, after a successful `builder` `run`. Selected agents run in the foreground: Pi waits for each `run` to finish and `Maestro`
-shows the current phase in Pi's status, while `pi-subagents` FleetView and `/subagents-fleet` show agent activity and transcripts.
+`Maestro` starts the `verifier`, when enabled, after a successful `builder` `run`. Selected agents use Pi's SDK and run one at a time in the foreground. Pi waits for each
+`run` to finish, and `Maestro` shows the current phase in Pi's status.
+
+When a saved native child session exists, `Maestro` displays its path on completion or failure. The `owner` can inspect that file directly or export it to HTML:
+
+```bash
+pi --export /sessions/weather/subagents/child.jsonl conversation.html
+```
 
 The `owner` must not edit product files while the workflow runs. `Maestro` can perform temporary experiments with `owner` agreement during `spec` preparation and
 permitted revisions. See [Workflow](docs/workflow.md#spec-approval).