@llblab/pi-actors 0.43.0 → 0.44.0

package/docs/README.md

@@ -4,16 +4,13 @@ Living index of all documentation in the `/docs` directory.
 
 ## Documents
 
-- [0.43-baseline.md](./0.43-baseline.md) — Frozen `0.42.3` line counts and retained-invariant preservation gate
-- [actors-deep-reference.md](./actors-deep-reference.md) — Recipe navigator, operating patterns, lifecycle discipline, and pitfalls
 - [command-templates.md](./command-templates.md) — Portable synchronous command execution standard
 - [template-recipes.md](./template-recipes.md) — Saved JSON/Markdown recipe standard, imports, and reusable command-template graph composition
 - [async-runs.md](./async-runs.md) — Run lifecycle, state, Control, Trace, cancellation, and terminal reconciliation
 - [actor-inspector.md](./actor-inspector.md) — Owner-filtered actor-instance navigation through Recipe, Trace, and Control
 - [tool-registry.md](./tool-registry.md) — Local `pi-actors` registry storage and `register_tool` adaptation
 - [recipe-library.md](./recipe-library.md) — Packaged standard recipe library such as async subagents, coordinator pipelines, utilities, and music playback
-- [task-first-recipes.md](./task-first-recipes.md) — Task-first design map for deriving high-level recipes and missing component cells
-- [component-recipes.md](./component-recipes.md) — Weak component-recipe contract for composing subagent coordinator building blocks
+- [releasing.md](./releasing.md) — Guarded tag validation, npm Trusted Publisher setup, registry verification, and GitHub Release convergence
 
 ## Root Context
 

package/docs/actor-inspector.md

@@ -18,13 +18,13 @@ Shows captured execution provenance:
 - declared artifacts and actor-local actions;
 - model/thinking policy and launch source.
 
-Captured Recipe evidence belongs to the Run generation and does not change when an active Recipe file later changes.
+Captured Recipe evidence belongs to the Run generation and does not change when an active Recipe file later changes. Non-empty object values render as indented brace-delimited property lists rather than flattened inline strings.
 
 ## Trace
 
 Shows the unified bounded Trace projection. Sources include lifecycle/runtime observations, Controls, owned Pi turns, command-log tails, results, artifacts, and diagnostics. Filter by source and open a row for structured detail.
 
-Trace ordering stays deterministic and newest-first. The projection applies path containment and redaction before rendering.
+Trace ordering stays deterministic and newest-first: timestamp descending, same-source physical ordinal descending, fixed internal source rank, then stable id. Internal ordinals are never displayed or interpreted as cross-source causality. Row numbers still read chronologically from bottom to top: the oldest visible event is `#1` and the newest carries the highest number. The summary states whether retained history is complete; `runtime.trace_compacted` means older history was discarded and shows bounded cumulative drop evidence. Terminal/result/execution/artifact evidence keeps its own authority. The projection applies path containment and redaction before rendering.
 
 ## Control
 
@@ -33,16 +33,17 @@ Shows:
 - Recipe-declared actor-local actions;
 - runtime-owned lifecycle actions;
 - generation-fenced endpoint readiness;
+- pending capacity, saturation, journal bytes, stale count, and diagnostics;
 - recent durable Control records and outcomes.
 
-A service endpoint counts as ready only when `control-endpoint.json` matches the Run's immutable `run_instance_id`.
+A service endpoint counts as ready only when `control-endpoint.json` matches the Run's immutable `run_instance_id`. Capacity reaches zero at 64 pending Controls; further requests are rejected before admission, while admitted nonterminal Controls never expire automatically. Runtime-owned kill remains available for a stuck saturated Run. Recent Control input and errors use the same bounded structured redaction as tool inspection. The durable `controls.jsonl` journal remains raw and local; rendering never mutates it or attaches an unredacted copy.
 
 ## Keys
 
 The footer displays current bindings. Use tab navigation to switch Recipe/Trace/Control, movement keys to select rows, detail navigation to inspect evidence, refresh to reconcile disk state, and the documented kill key for lifecycle termination.
 
-Run kill revalidates owner and generation through the canonical lifecycle path. The Inspector never edits state directly and never derives authority from displayed data.
+Run kill revalidates owner and generation through the canonical lifecycle path. After success, the Run status header is the sole confirmation; the content area does not duplicate it. The Inspector never edits state directly and never derives authority from displayed data.
 
 ## Scope
 
-The Actor Inspector treats each Run as a concrete actor instance. It does not expose group conversations, peer addresses, routing, or communication topology. Use `inspect target=runtime`, `inspect target=recipes`, and `inspect target=tool:<name>` for non-Run management targets.
+The Actor Inspector treats each Run as a concrete actor instance. It does not expose group conversations, peer addresses, routing, or communication topology. Use `inspect target=runtime view=status`, `inspect target=recipes view=status`, and `inspect target=tool:<name> view=status` for non-Run management targets.

package/docs/async-runs.md

@@ -55,9 +55,9 @@ Trace records strict bounded events:
 {"id":"…","ts":"…","kind":"command.done","summary":"Command completed","data":{"code":0},"level":"info","attention":"followup"}
 ```
 
-Required fields: `id`, `ts`, `kind`. Optional fields: `summary`, `data`, `level`, `attention`. Trace rejects addressed-envelope fields and malformed or oversized data.
+Required fields: `id`, `ts`, `kind`. Optional fields: `summary`, `data`, `level`, `attention`. Trace rejects addressed-envelope fields and malformed or oversized data. It retains a recent suffix within 2,048 events and 4 MiB. When either bound would be exceeded, the canonical lock atomically keeps a newest suffix near the lower targets, the new event, and one cumulative warning-only `runtime.trace_compacted` marker. The marker means older history was discarded; it reports cumulative drop evidence and never requests attention.
 
-Runtime lifecycle, runner progress, command completion, cancellation, kill, parent teardown, and controlled-service observations use Trace. `inspect view=trace` projects these events with Controls, owned Pi turns, logs, results, artifacts, and diagnostics under a deterministic global bound.
+Runtime lifecycle, runner progress, command completion, cancellation, kill, parent teardown, and controlled-service observations use Trace. Bounded reads preserve complete UTF-8 lines and disclose omitted legacy prefixes. `inspect view=trace` reports retained-history completeness and projects events with Controls, owned Pi turns, logs, results, artifacts, and diagnostics newest-first. Equal timestamps use same-source physical order, then fixed source rank and stable id without claiming cross-source causality. Terminal state, `result.json`, `execution.json`, and artifacts remain authoritative even when old Trace has compacted.
 
 ## Control
 
@@ -82,15 +82,15 @@ The runtime:
 5. writes the exact `{id, action, input?}` wire document to FIFO or named pipe;
 6. records delivered or failed outcome.
 
-Unix services may publish a FIFO; native Windows services publish a Windows named pipe. Native Windows FIFO delivery fails before transport rather than degrading to another protocol. FIFO wire documents above the portable 512-byte atomic-write bound fail before writing; named pipes retain the general Control input bound.
+Unix services may publish a FIFO; native Windows services publish a Windows named pipe. Native Windows FIFO delivery fails before transport rather than degrading to another protocol. Both transports admit the same portable envelope: action is at most 64 lowercase ASCII characters, serialized JSON input is at most 380 bytes, and the newline-terminated wire record is at most 512 bytes. Invalid envelopes fail before journal admission or transport. Put larger data in a declared artifact/path and send only a bounded reference or instruction through Control.
 
-A service claims queued or transport-delivered Controls and records handled/failed outcomes under the token-owned Control journal lock. Journal snapshots replace atomically, and expected-status fencing prevents delivery failure evidence from regressing a Control already claimed or completed by a fast consumer. Terminal compaction remains bounded. Services capture their startup generation, so stale-generation Controls never execute.
+A service exact-id claims queued or transport-delivered Controls and records handled/failed outcomes through the canonical Control journal authority. Admission performs one locked read, integrity/generation check, terminal-tail compaction, capacity decision, and atomic write. The 65th pending Control and a rewrite exceeding 1 MiB fail as bounded `control_backpressure` before admission; malformed, unreadable, oversized, or stale-generation journals fail with an integrity reason and no rejected record. `inspect view=control` reports pending capacity, saturation, stale work, journal bytes, and diagnostics. Every transition uses the same lock, expected-state fence, 128-terminal compaction, and atomic bounded rewrite; persisted errors truncate inside the string at 4 KiB. Admitted nonterminal Controls never expire automatically. Delivery failure evidence cannot regress a Control already claimed or completed by a fast consumer. Services capture their startup generation, so stale-generation Controls never execute.
 
-Runtime lifecycle `kill`, retention actions, and review retry/reset remain runtime-owned rather than Recipe-declared.
+Runtime lifecycle `kill`, retention actions, and review retry/reset remain runtime-owned rather than Recipe-declared. Kill is the recovery path for a stuck saturated Run: it bypasses actor-local Control capacity and creates no synthetic Control. Same-directory restart clears all generation-local evidence before the new `run_instance_id`; archive moves the exact bounded terminal tree, while prune removes kernel state and preserves only explicitly requested artifacts.
 
 ## Execution Evidence
 
-`execution.json` stores general command/session provenance. The async runner keeps bounded stdout/stderr logs plus bounded complete captures when semantic validation requires untruncated evidence. Pi command execution also records owned session provenance for later Trace projection and review checks.
+`execution.json` stores general command/session provenance. The async runner keeps bounded stdout/stderr logs plus complete capture artifacts when semantic validation requires untruncated evidence. Pi command execution also records owned session provenance for later Trace projection and review checks. Trace and Control quotas do not constrain declared user artifacts, repositories or media sources, complete execution captures, or actor-owned queue/workload state; each remains governed by its own lifecycle and policy.
 
 Review acceptance remains a command-stage concern. General execution evidence does not imply review approval.
 
@@ -98,7 +98,7 @@ Review acceptance remains a command-stage concern. General execution evidence do
 
 Statuses include `running`, `done`, `failed`, `exited`, `cancelled`, and `killed`. Status resolution combines persisted metadata, result/terminal evidence, and verified process state.
 
-Ambient observation detects terminal transitions and Trace attention. Terminal follow-up delivery persists handled/failure evidence so reloads retry unhandled transitions without duplicating completed notifications.
+Ambient observation detects terminal transitions and retained Trace attention. Canonical attention is an in-memory wake hint, not a durable queue: observers prime retained ids at startup, deliver each later retained unseen id once, and bound memory to the current retained set across compaction. Persist durable recovery state or an artifact before emitting attention; compaction may discard older hints and its marker makes that history loss explicit. Terminal follow-up delivery persists handled/failure evidence so reloads retry unhandled transitions without duplicating completed notifications.
 
 Large semantic results stay outside compact visible follow-up text and remain available in structured details, execution captures, or artifacts.
 
@@ -124,7 +124,9 @@ Archive and prune apply only to terminal Runs and enforce path containment. Rete
 Packaged controlled services demonstrate the endpoint protocol:
 
 - `music-player` consumes playback Controls and emits playback Trace;
-- `resource-locker` consumes queue/lease actions and emits lock Trace.
+- `resource-locker` consumes queue/lease actions, emits lock Trace, and atomically retains at most 512 valid journal records within 1 MiB.
+
+Shared archive/prune evidence similarly retains at most 256 valid records within 1 MiB under its canonical lock. The obsolete advisory `wake.jsonl` notifier was removed; filesystem watchers and bounded reconciliation observe authoritative state directly.
 
 One-shot pipelines omit Control and terminate through their command graph.
 
@@ -136,4 +138,4 @@ inspect target=run:<id> view=trace source=lifecycle lines=40
 inspect target=run:<id> view=control
 ```
 
-Use `/actor-inspector` to inspect Runs as concrete actor instances in the live TUI. Runtime, Recipe registry, and tool definitions remain separate management targets.
+Use `/actor-inspector` to inspect Runs as concrete actor instances in the live TUI. Runtime, Recipe registry, and tool definitions remain separate management targets. No public noun, tool, target, or view is added by bounded retention.

package/docs/command-templates.md

@@ -16,7 +16,7 @@ Layer boundary: command templates own only the synchronous execution graph. Reci
 
 Command-template standard owns:
 
-- Command string splitting and direct argv execution.
+- Command string splitting, portable script-interpreter inference, and direct argv execution.
 - Placeholder resolution, typed public args, defaults, `??`, ternary string selection, and array-index placeholders.
 - Synchronous graph shape: sequence, `parallel`, `when`, `repeat`, stdin flow, stdout joins, and output selection.
 - Per-node execution controls: `timeout`, `delay`, `retry`, `failure`, and `recover`.
@@ -72,7 +72,7 @@ A runtime must:
 
 1. Split the template into shell-like words with simple single quotes, double quotes, and backslash escapes
 2. Substitute placeholders inside each split word
-3. Execute command + args directly, without shell evaluation
+3. Infer a first-word `.js` or `.mjs` script through the first available `node`, `bun`, or `deno run` runtime, infer `.sh` through `bash`, and otherwise execute command + args directly; explicit interpreters remain unchanged and no shell evaluates the resulting argv
 4. Treat exit code `0` as success and non-zero as failure
 5. Use stdout as the default result channel and stderr only for diagnostics
 
@@ -106,35 +106,11 @@ With runtime values `{ "text": "hello" }`, argv is:
 
 Use `defaults` for visible configuration data; use inline defaults for compact local literals. Prefer flag-style examples such as `/path/to/tool --file {file} --lang {lang=ru}` for readability, but positional forms such as `/path/to/tool {file} {lang=ru}` are valid when the invoked script defines that CLI contract.
 
-Fallback values can be selected with nullish coalescing:
-
-```json
-{
-  "template": "deploy --env {env??dev} --region {region??local}"
-}
-```
-
-Optional flags can be mapped from boolean args with a ternary:
-
-```json
-{
-  "args": ["target:path", "all:bool"],
-  "defaults": { "all": "true" },
-  "template": "validate-recipe {target} {all?--all:}"
-}
-```
+Use `{env??dev}` for fallback values and `{all?--all:}` to map boolean args to optional text.
 
 Typed declarations annotate the public tool interface, not the shell command. They may live in `args` or inline placeholders such as `{request_timeout:int=60000}` and `{mode:enum(check,fix)=check}`. Use metadata-first authoring (`args` plus `defaults`) when long templates should stay visually short; use inline-first authoring when one self-contained `template` property is clearer. They do not sandbox or reinterpret the executable; they only let the host generate narrower input schemas and normalize runtime values before placeholder substitution. Untyped `args` and untyped placeholders continue to work unchanged.
 
-Node control fields can also read public args. Use distinct arg names so execution controls stay visually separate from public inputs:
-
-```json
-{
-  "args": ["timeout_ms:int"],
-  "timeout": "{timeout_ms}",
-  "template": "npm test"
-}
-```
+Node control fields can also read public args, for example `"timeout": "{timeout_ms}"`; use distinct names so execution controls stay visually separate from public inputs.
 
 ## Quoting
 
@@ -194,21 +170,6 @@ Composition rules:
 - `min_successful` adds a join header with `complete`, `degraded`, or `insufficient_data`; with `failure: "branch"` or `"root"`, an unmet threshold fails at that scope
 - Each leaf still applies its own inline defaults
 
-```json
-{
-  "template": [
-    "/path/to/tts --text {text} --lang {lang} --out {mp3}",
-    {
-      "defaults": { "codec": "libopus" },
-      "template": "ffmpeg -y -i {mp3} -c:a {codec} {ogg}"
-    }
-  ],
-  "args": ["text", "lang", "mp3", "ogg"],
-  "defaults": { "lang": "en" },
-  "output": "ogg"
-}
-```
-
 `output` selects the primary result channel. Omitted `output` means `"stdout"`, and explicitly writing `"output": "stdout"` is valid standard syntax. Artifact-producing handlers may instead name a runtime value or placeholder path, e.g. `"ogg"` or `"{ogg}"`. Do not use `artifacts` in command-template nodes; named artifact manifests belong to the template-recipe layer.
 
 ### Repeat
@@ -245,52 +206,7 @@ Repeat expressions support only integers, `index`, `prev`, `next`, `repeat`, par
 
 Repeat placeholders are local generated values. Call-time args should not use these reserved names to override the repeat index.
 
-Parallel nodes use the same object shape. Flags come first and `template` stays last:
-
-```json
-{
-  "template": [
-    "prepare {out_dir}",
-    {
-      "parallel": true,
-      "template": [
-        {
-          "label": "reviewer-a",
-          "timeout": 300000,
-          "template": "review-gpt {scope}"
-        },
-        {
-          "label": "reviewer-b",
-          "timeout": 300000,
-          "template": "review-deepseek {scope}"
-        },
-        {
-          "label": "kimi",
-          "timeout": 300000,
-          "template": "review-kimi {scope}"
-        }
-      ]
-    },
-    "merge {out_dir}"
-  ]
-}
-```
-
-A degraded parallel join is still usable when at least one branch succeeds:
-
-```text
---- branch: reviewer-a status: done ---
-review text
---- branch: reviewer-b status: failed ---
-exit: 1
-stderr: provider balance exhausted
-```
-
-Some local schemas may accept `pipe` as an alias, but the portable standard is `template: [...]`.
-
-## Fail-Open Default Policy
-
-By default, composition continues on failure: the failed step is logged and the next step executes. This is analogous to `make -k` — the user sees all failures at once and decides what to fix.
+Parallel children use the same object shape: flags come first and `template` stays last. A join remains usable when at least one branch succeeds and reports each branch label/status. Some local schemas may accept `pipe`, but the portable standard is `template: [...]`.
 
 ## Failure Propagation
 
@@ -302,33 +218,7 @@ Use `failure` when a node should stop more aggressively:
 - `"branch"`: stop the current sequence/subtree and return a failed branch to the nearest parent. In a parallel node, sibling branches keep running and the join becomes degraded. At the root, branch failure is still a tool failure.
 - `"root"`: abort the outermost composition.
 
-```json
-{
-  "parallel": true,
-  "template": [
-    {
-      "label": "agent-a",
-      "failure": "branch",
-      "template": [
-        "agent-a-work {scope}",
-        "agent-a-validate {scope}",
-        "agent-a-push {scope}"
-      ]
-    },
-    {
-      "label": "agent-b",
-      "failure": "branch",
-      "template": [
-        "agent-b-work {scope}",
-        "agent-b-validate {scope}",
-        "agent-b-push {scope}"
-      ]
-    }
-  ]
-}
-```
-
-If `agent-a-validate` fails, `agent-a-push` is skipped, `agent-b` can still finish, and the parallel join reports degraded branch coverage.
+A branch failure skips the remainder of that branch while parallel siblings can finish; their join reports degraded coverage.
 
 ## Retry
 

package/docs/recipe-library.md

@@ -35,9 +35,9 @@ Artifact pipelines terminate in files/manifests and result evidence; they do not
 ### Controlled services
 
 - `music-player.json` — playback service with declared playback actions, `controls.jsonl`, generation-fenced endpoint readiness, state artifact, and playback Trace. Player selection is `player:enum(auto,mpv,afplay,ffplay,cvlc,play,wmp)=auto`.
-- `resource-locker.json` — optional queue/lease-lock service with explicit owner/resource input and lock Trace.
+- `resource-locker.json` — optional queue/lease-lock service with explicit owner/resource input, lock Trace, and a 512-record/1 MiB atomically retained journal.
 
-These are the packaged Recipes that declare actor-local Control. Ordinary one-shot Recipes omit it.
+These are the packaged Recipes that declare actor-local Control. Ordinary one-shot Recipes omit it. Helper-backed packaged Recipes self-locate their installed package root when `repo` is omitted; an explicit caller value still wins for development or custom layouts.
 
 ## Component Recipes
 
@@ -64,7 +64,7 @@ Use utilities as imported cells or registered tools where their contract fits.
 3. Use inline templates for genuinely one-off trusted work.
 4. Declare artifacts for outputs that callers must retain.
 5. Declare Control only when a service process actually consumes it.
-6. Keep large semantic evidence in artifacts or execution captures, not Trace summaries.
+6. Keep large semantic evidence in artifacts or execution captures, not Trace summaries; Trace/Control quotas do not bound user artifacts or actor-owned workload state.
 
 ## Installation Safety
 
@@ -76,12 +76,10 @@ Do not bulk-copy `recipes/*.json` into the user Recipe root. Internal `draft-rev
 npm run recipes:qa
 ```
 
-Recipe QA validates syntax, imports, Control declarations, artifact paths, helper references, and platform documentation. Removed mailbox declarations fail with the migration diagnostic rather than receiving automatic conversion.
+Recipe QA validates syntax, imports, Control declarations, artifact paths, helper references, and platform documentation. Recipe descriptions are optional because discovery supplies stable fallback tool copy; internal component Recipes do not need boilerplate. The packaged baseline requires zero diagnostics and zero warnings, and any future warning is release-blocking with its concrete file and repair. Removed mailbox declarations fail with the migration diagnostic rather than receiving automatic conversion.
 
 ## Related
 
 - [Template Recipes](./template-recipes.md)
 - [Command templates](./command-templates.md)
 - [Runs](./async-runs.md)
-- [Component Recipes](./component-recipes.md)
-- [Task-first design](./task-first-recipes.md)

package/docs/releasing.md

@@ -0,0 +1,28 @@
+# Release Operations
+
+Stable releases use one immutable tag workflow. The workflow runs the complete reusable Ubuntu, macOS, Windows, and dependency-audit boundary before any publication, publishes and verifies the exact npm package through Trusted Publisher, then creates or converges the GitHub Release from the matching changelog section.
+
+## One-time npm Trusted Publisher setup
+
+Configure the existing public package `@llblab/pi-actors` on npmjs.com with a GitHub Actions Trusted Publisher using these exact values:
+
+- **Owner:** `llblab`
+- **Repository:** `pi-actors`
+- **Workflow filename:** `release.yml`
+- **Environment:** Leave empty unless the workflow and npm configuration later adopt the same named GitHub environment in one reviewed change.
+
+The binding must target `.github/workflows/release.yml`; npm asks for the filename rather than the repository-relative path. npm does not verify this identity when the setting is saved, so the first tagged publication provides the decisive proof.
+
+Do not create `NPM_TOKEN`, `NODE_AUTH_TOKEN`, or another long-lived npm publish secret. The publication job runs on a GitHub-hosted Ubuntu runner with `id-token: write`, Node 24, npm 11.5.1 or newer, the public npm registry, and package-manager caching disabled at the credential-bearing boundary.
+
+## Release sequence
+
+1. Merge the validated release tree through the repository's guarded `dev` to `main` flow.
+2. Create one immutable `v<package.version>` tag on the verified `main` commit.
+3. Let `.github/workflows/release.yml` invoke the complete reusable validation workflow.
+4. Let the publication job verify the tag commit, package manifests, and non-empty changelog section.
+5. Publish the exact public npm package through OIDC when the version does not exist.
+6. Verify npm version, `gitHead`, Pi extension/skill metadata, and packed runtime manifests.
+7. Create or update the GitHub Release only after npm verification succeeds.
+
+A rerun skips `npm publish` only when the exact existing version reports the same tagged `gitHead`; contradictory identity fails closed because npm versions are immutable. Registry lookup retries remain bounded. A missing or mismatched Trusted Publisher usually surfaces as npm authentication or not-found failure and must be corrected in npm package settings—never by adding a token fallback.

package/docs/template-recipes.md

@@ -87,7 +87,7 @@ Only a process that consumes actor-local input declares actions:
 }
 ```
 
-Actions must be lowercase, unique, and non-reserved. One-shot Recipes omit Control. Outputs belong in Trace, artifacts, execution evidence, or the command result.
+Actions must be lowercase ASCII, unique, non-reserved, and at most 64 characters. Serialized Control input is at most 380 bytes so every admitted wire record remains within 512 bytes on FIFO and named pipe. One-shot Recipes omit Control. Larger data belongs in a declared artifact/path; outputs belong in Trace, artifacts, execution evidence, or the command result.
 
 ## Artifacts
 

package/docs/tool-registry.md

@@ -27,8 +27,8 @@ User Recipes take priority over packaged Recipes. Active invalid or disabled sha
 Inspect registry state with:
 
 ```text
-inspect target=recipes
-inspect target=tool:<name>
+inspect target=recipes view=status
+inspect target=tool:<name> view=status
 ```
 
 Recipe inspection reports active, shadowed, invalid, disabled, diagnostic, risk, usage, and review evidence. Tool inspection reports the current capability definition/schema; a registered tool is not a running actor.

package/index.ts

@@ -110,7 +110,7 @@ export default function toolRegistryExtension(pi: Pi.ExtensionAPI) {
         Tools.resolveActiveRuntimeTool(name, runtime.getTools(), (activeName) =>
           actorToolDefinitions.get(activeName),
         ),
-      handleRuntimeMessage: automaticReview.handleMessage,
+      handleRuntimeControl: automaticReview.handleControl,
       registryRuntime: runtime,
       setActiveTools: (toolNames) => pi.setActiveTools(toolNames),
     }).map(withCurrentThinkingContext),

package/lib/async-runs.ts

@@ -59,14 +59,11 @@ import {
   verifyRunProcessIdentity,
   type RunProcessIdentity,
 } from "./runs-process.ts";
+import * as RuntimeIdentity from "./runtime-identity.ts";
 import * as RunsStart from "./runs-start.ts";
 import { appendRunTraceEvent } from "./runs-trace.ts";
 import * as RunsIndex from "./runs-index.ts";
 import * as RunsParentTeardown from "./runs-parent-teardown.ts";
-import {
-  appendRunControlInStateDir,
-  updateRunControlStatusInStateDir,
-} from "./runs-controls.ts";
 import {
   deliverRunControl,
   type DeliverRunControlOptions,
@@ -173,7 +170,7 @@ export interface AsyncRunMeta {
   run: string;
   run_instance_id: string;
   state_dir: string;
-  state_schema: "run-kernel-v1";
+  state_schema: typeof RuntimeIdentity.RUN_STATE_SCHEMA;
   status: AsyncRunStatus;
   tool?: string;
   template: CommandTemplateValue;
@@ -466,7 +463,22 @@ export function startRun(
   const resolved = resolveRunTemplate(startParams);
   const run = safeRunId(startParams.run_id);
   const stateDir = resolveStateDir(startParams, run);
+  const recipeFile = startParams.file
+    ? resolveRecipeFile(startParams.file)
+    : undefined;
+  const packagedRecipeRoot = resolve(Paths.getPackagedRecipeRoot());
+  const recipeRelation = recipeFile
+    ? relative(packagedRecipeRoot, recipeFile)
+    : undefined;
+  const packagedRepo =
+    startParams.defaults?.repo === "~/.pi/agent/extensions/pi-actors" &&
+    recipeRelation &&
+    !recipeRelation.startsWith("..") &&
+    !isAbsolute(recipeRelation)
+      ? dirname(packagedRecipeRoot)
+      : undefined;
   const values = {
+    ...(packagedRepo ? { repo: packagedRepo } : {}),
     ...(startParams.values || {}),
     run_id: run,
     state_dir: stateDir,
@@ -494,9 +506,6 @@ export function startRun(
     prepareStateDirForStart(stateDir);
     const stdout = join(stateDir, "stdout.log");
     const stderr = join(stateDir, "stderr.log");
-    const recipeFile = startParams.file
-      ? resolveRecipeFile(startParams.file)
-      : undefined;
     const recipe = startParams.name || getRunIdFromFile(recipeFile);
     const includeActorRecipeContext =
       startParams.actor_context !== false &&
@@ -545,7 +554,7 @@ export function startRun(
       run,
       run_instance_id: randomUUID(),
       state_dir: stateDir,
-      state_schema: "run-kernel-v1",
+      state_schema: RuntimeIdentity.RUN_STATE_SCHEMA,
       status: "running",
       ...(startParams.tool ? { tool: startParams.tool } : {}),
       template: resolved.template,
@@ -920,37 +929,9 @@ function stopRun(
     ) {
       return { stopped: false, reason: "run generation changed", status };
     }
-    const control =
-      event === "run.kill" && typeof status.run_instance_id === "string"
-        ? appendRunControlInStateDir(stateDir, {
-            action: "kill",
-            run_instance_id: status.run_instance_id,
-          })
-        : undefined;
-    if (control) {
-      updateRunControlStatusInStateDir(
-        stateDir,
-        control.id,
-        "claimed",
-        {},
-        ["queued"],
-      );
-    }
-    const finish = (result: Record<string, unknown>): Record<string, unknown> => {
-      if (!control) return result;
-      const handled = result.stopped === true;
-      updateRunControlStatusInStateDir(
-        stateDir,
-        control.id,
-        handled ? "handled" : "failed",
-        handled ? {} : { error: String(result.reason ?? "kill rejected") },
-        ["claimed"],
-      );
-      return { ...result, control_id: control.id };
-    };
     const pid = Number(status.pid || 0);
     if (status.status !== "running" && status.status !== "exited") {
-      return finish({ stopped: false, reason: "not running", status });
+      return { stopped: false, reason: "not running", status };
     }
     const identity = verifyRunProcessIdentity(
       pid,
@@ -961,22 +942,22 @@ function stopRun(
         identity.status === "owner_mismatch" ||
         identity.status === "unsupported_proof"
       ) {
-        return finish({
+        return {
           stopped: false,
           reason: identity.status.replaceAll("_", " "),
           process_identity_status: identity.status,
           status,
-        });
+        };
       }
-      return finish({ stopped: false, reason: "not running", status });
+      return { stopped: false, reason: "not running", status };
     }
     if (!identity.valid) {
-      return finish({
+      return {
         stopped: false,
         reason: identity.status.replaceAll("_", " "),
         process_identity_status: identity.status,
         status,
-      });
+      };
     }
     let signalResult: RunProcessSignalPlan;
     try {
@@ -986,11 +967,6 @@ function stopRun(
         status.process_identity as RunProcessIdentity,
       );
     } catch (error) {
-      if (control) {
-        updateRunControlStatusInStateDir(stateDir, control.id, "failed", {
-          error: error instanceof Error ? error.message : String(error),
-        });
-      }
       throw error;
     }
     appendRunTraceEvent(stateDir, {
@@ -1007,13 +983,13 @@ function stopRun(
       finalizeInterruptedExecution(stateDir, "cancelled", signal);
       markTerminalProgress(stateDir, "cancelled");
     }
-    return finish({
+    return {
       stopped: true,
       pid,
       signal,
       ...signalResult,
       state_dir: stateDir,
-    });
+    };
   } finally {
     releaseControlLock();
   }

package/lib/automatic-review-runtime.ts

@@ -16,7 +16,7 @@ import * as ToolReviewScheduler from "./tool-review-scheduler.ts";
 
 export interface AutomaticReviewRuntime {
   close(): void;
-  handleMessage(type: string, body: unknown): Record<string, unknown>;
+  handleControl(action: string, input: unknown): Record<string, unknown>;
   schedule(): void;
   start(ctx: Pi.ExtensionContext): void;
 }
@@ -52,18 +52,18 @@ export function createAutomaticReviewRuntime(
 
   return {
     close,
-    handleMessage(type, body) {
-      if (type !== "review.retry" && type !== "review.reset") {
-        throw new Error("tool:pi-actors accepts review.retry or review.reset messages.");
+    handleControl(action, input) {
+      if (action !== "review.retry" && action !== "review.reset") {
+        throw new Error("runtime accepts review.retry or review.reset Controls.");
       }
-      if (type === "review.retry" && !Paths.isAutomaticRecipeReviewEnabled()) {
+      if (action === "review.retry" && !Paths.isAutomaticRecipeReviewEnabled()) {
         throw new Error(
           "Automatic recipe review is disabled by PI_ACTORS_AUTOMATIC_REVIEW.",
         );
       }
       return ReviewControl.controlAutomaticReview(
-        type,
-        ReviewControl.parseAutomaticReviewScope(body),
+        action,
+        ReviewControl.parseAutomaticReviewScope(input),
         {
           scheduleDraft: () => draftScheduler?.schedule(),
           scheduleTool: () => toolScheduler?.schedule(),