@elpapi42/pi-fleet 0.1.0-beta.8 → 0.1.0-beta.9

package/CHANGELOG.md

@@ -11,6 +11,31 @@
 - Contained asynchronous coordinator event/store failures by stopping the affected Pi process and rejecting waiters instead of producing unhandled promise rejections.
 - Added a nightly reliability workflow and an isolated soak suite covering 500 concurrent ordered sends and 100 name lifecycle cycles.
 - Reject invalid UTF-8 in stdin and Pi RPC stdout instead of silently replacing bytes at either protocol boundary.
+- Keep idle agents `idle + absent` after Fleet-initiated orderly shutdown even when Pi reports a nonzero exit; active work remains `failed/runtime_interrupted`.
+- Align explicit stdin input with the runtime's 512 KiB message limit and document credential-environment and receive-timeout behavior before the quick start.
+- Install native services without forcing the default persistent state directory into `PIFLEET_STATE_ROOT`, preserving the default split between durable SQLite state and the private runtime socket.
+- Validated systemd user lingering, idle reboot restoration, active reboot interruption without replay, single-writer restoration, and session preservation in a disposable privileged systemd container.
+- Added a fail-closed production-audit policy that permits only `GHSA-3jxr-9vmj-r5cp` at the exact `brace-expansion@5.0.6` path pinned by managed Pi `0.80.10`; every changed or additional vulnerability still blocks release.
+
+## 0.1.0-beta.9 — 2026-07-20
+
+Core product and Linux supervision validation after beta.8.
+
+### Fixed
+
+- An orderly Fleet shutdown now leaves idle agents `idle + absent` even if Pi reports a nonzero exit; active interrupted work still becomes `failed/runtime_interrupted` without replay.
+- A clean native-service install no longer forces the default persistent state directory into `PIFLEET_STATE_ROOT`, so the service and ordinary CLI agree on the private runtime socket while SQLite remains in durable state storage.
+- Explicit stdin now uses the runtime's default 512 KiB message boundary instead of accepting a larger payload that the runtime later rejects.
+- Onboarding now explains persistent credential environments before the first operational command and uses explicit receive timeout units.
+
+### Validated
+
+- Reused one real named agent across a service restart and related follow-up assignment with the same native Pi session and less re-explanation.
+- Proved user lingering, idle PID-1 restart without eager restoration, single-writer session restoration, active restart interruption without replay, explicit recovery, and session preservation in a disposable systemd container.
+
+### Security
+
+- The production audit remains fail-closed except for one deliberate exact exception: managed Pi `0.80.10` currently pins `brace-expansion@5.0.6` affected by local glob-input denial-of-service advisory `GHSA-3jxr-9vmj-r5cp`. The policy verifies the advisory, package versions, and installed path and rejects every additional or changed vulnerability. Upstream tracking is `earendil-works/pi#6882`.
 
 ## 0.1.0-beta.8 — 2026-07-20
 

package/README.md

@@ -8,7 +8,7 @@ create · send · receive · status · list · watch · destroy
 
 Fleet keeps a Pi process resident when possible, restores it from the same native Pi session when absent, accepts repeated steering input, and returns the latest assistant message after Pi becomes idle. Pi sessions remain under your control: Fleet references them but never copies or deletes them.
 
-> **Beta:** `0.1.0-beta.8` has passed deterministic Linux x64 fault, recovery, package, compatibility, and resource-stability tests with Pi `0.80.10`. Its tag workflow requires a fresh registry-install operational smoke, and direct isolated testing covers lifecycle, timeout, repeated receive, raw watch and pipe disconnection, session mutation and selectors, concurrency, Pi/runtime crash recovery, capacity, interrupted-work responses, provider failures, extension UI cancellation, and failed restoration. Actual logout/reboot recovery, macOS launchd/containment, automatic upgrades, and public service-management UX are not yet release-validated.
+> **Beta:** `0.1.0-beta.9` has passed deterministic Linux x64 fault, recovery, package, compatibility, systemd/PID-1 restart, and resource-stability tests with Pi `0.80.10`. Its tag workflow requires a fresh registry-install operational smoke, and direct isolated testing covers lifecycle, timeout, repeated receive, raw watch and pipe disconnection, session mutation and selectors, concurrency, Pi/runtime crash recovery, capacity, interrupted-work responses, provider failures, extension UI cancellation, and failed restoration. Actual logout/reboot recovery, macOS launchd/containment, automatic upgrades, and public service-management UX are not yet release-validated.
 
 ## Install
 
@@ -23,12 +23,17 @@ Install the beta globally:
 ```bash
 npm install --global @elpapi42/pi-fleet@beta
 pifleet --version
+```
+
+Configure normal Pi provider credentials **before the first operational Fleet command**. `list`, `create`, and the other operational commands start or reuse one persistent runtime; a variable supplied only to a later command, such as `ANTHROPIC_API_KEY=… pifleet create …`, does not replace that runtime's environment. Put provider credentials in Pi's credential configuration or the persistent service/runtime environment, then verify startup:
+
+```bash
 pifleet list
 ```
 
 `npx @elpapi42/pi-fleet@beta` is suitable for evaluation, but a global installation is recommended for continued use. Fleet materializes a verified runtime independently of the npm installation/cache, and evaluation can leave that runtime and Fleet state behind intentionally.
 
-Pi Fleet includes the tested Pi coding-agent package. It uses your normal Pi configuration, provider credentials, extensions, skills, and project resources. **Do not put API keys or other secrets in CLI arguments:** Fleet persists accepted Pi arguments so it can restore the agent. Use Pi's credential configuration or provider environment variables instead.
+Pi Fleet includes the tested Pi coding-agent package. It uses your normal Pi configuration, provider credentials, extensions, skills, and project resources. **Do not put API keys or other secrets in CLI arguments:** Fleet persists accepted Pi arguments so it can restore the agent.
 
 ## Quick start
 
@@ -42,7 +47,7 @@ Send work and retrieve the latest assistant message after Pi becomes idle:
 
 ```bash
 pifleet send reviewer "Review the authentication changes"
-pifleet receive reviewer --human
+pifleet receive reviewer --timeout 10m --human
 ```
 
 Inspect and remove Fleet management:
@@ -69,7 +74,7 @@ pifleet destroy NAME [--human]
 
 Finite commands emit JSON by default. Add `--human` for concise human output. `watch` has no human mode: stdout is only raw, complete records appended to the selected Pi session JSONL.
 
-Messages can be read explicitly from stdin with `-`:
+Messages can be read explicitly from stdin with `-` and are limited to 512 KiB by default:
 
 ```bash
 git diff | pifleet send reviewer -
@@ -118,6 +123,7 @@ Positional Pi prompts and `@file` inputs after `--` are rejected; use Fleet's op
 - when already idle, it returns immediately;
 - with no assistant message, it returns `no_response`;
 - `--timeout 0` performs an immediate poll;
+- use an explicit duration suffix such as `30s`, `5m`, or `1h`; a unitless value is milliseconds;
 - timing out does not cancel or change Pi.
 
 ## Sessions and `watch`
@@ -174,10 +180,11 @@ Do not include API keys, message contents, session contents, or private paths un
 ## Beta limitations
 
 - Current deterministic reliability and documented global-install package validation cover Linux x64 only. Arbitrarily hoisted local-prefix, pnpm, and unusual `npx` dependency layouts are not yet supported.
-- Actual logout and host reboot recovery remain unvalidated.
+- Disposable systemd/PID-1 restart and user-lingering recovery are validated; a full host logout and kernel reboot remain unvalidated.
 - launchd and macOS descendant containment remain unvalidated.
 - Real disk-exhaustion behavior and multi-hour resource growth remain unvalidated; bounded SQLite and in-process resource tests are covered.
 - Native service install/repair/uninstall exists internally but has no supported public UX yet.
+- Managed Pi `0.80.10` pins `brace-expansion@5.0.6`, which has the local glob-input denial-of-service advisory `GHSA-3jxr-9vmj-r5cp`. Beta.9 carries a narrow, visible audit exception for only that exact package, version, path, and advisory; any other production vulnerability still fails the release gate. Upstream tracking: [earendil-works/pi#6882](https://github.com/earendil-works/pi/issues/6882).
 - Runtime upgrades are not automatic; active runtimes are not silently replaced.
 - Session tails cannot promise exactly-once behavior under arbitrary external mutation.
 - A promptless missing session path may remain physically unmaterialized until Pi writes conversation content, following native Pi behavior.

package/dist/cli-meta.json

@@ -156,7 +156,7 @@
       "format": "esm"
     },
     "src/cli/input.ts": {
-      "bytes": 977,
+      "bytes": 976,
       "imports": [],
       "format": "esm"
     },
@@ -593,7 +593,7 @@
       "imports": [],
       "exports": [],
       "inputs": {},
-      "bytes": 270235
+      "bytes": 270234
     },
     "dist/cli.mjs": {
       "imports": [
@@ -780,7 +780,7 @@
           "bytesInOutput": 140
         },
         "src/cli/input.ts": {
-          "bytesInOutput": 841
+          "bytesInOutput": 840
         },
         "src/cli/output.ts": {
           "bytesInOutput": 1016
@@ -837,7 +837,7 @@
           "bytesInOutput": 1191
         }
       },
-      "bytes": 150476
+      "bytes": 150475
     }
   }
 }

package/dist/cli.mjs

@@ -3385,7 +3385,7 @@ function splitArgv(argv) {
 
 // src/shared/product-identity.ts
 var PRODUCT_BINARY = "pifleet";
-var PRODUCT_VERSION = "0.1.0-beta.8";
+var PRODUCT_VERSION = "0.1.0-beta.9";
 
 // src/cli/commands/create.ts
 import { resolve } from "node:path";
@@ -3397,7 +3397,7 @@ function isAgentName(value) {
 }
 
 // src/cli/input.ts
-var DEFAULT_MAX_INPUT_BYTES = 1024 * 1024;
+var DEFAULT_MAX_INPUT_BYTES = 512 * 1024;
 async function resolveMessageInput(value, stdin, maxBytes = DEFAULT_MAX_INPUT_BYTES) {
   if (value !== "-") return requireContent(value);
   const chunks = [];