@amaster.ai/employee-runtime-connector 0.1.13-beta.2 → 0.1.14

package/README.md

@@ -102,8 +102,10 @@ each authorized value through `browser_read_credential`. Desktop-delegated,
 same-UID, and non-Pi runners must not advertise or execute this capability.
 
 `browser_credential_auth_transaction_v1` remains build/runtime vocabulary for the
-older private-FD prototype and is advertised only if its complete Pi browser TCB
-is present. New browser-credential dispatches require
+private-FD path and is advertised only when the sealed extension matches its pinned
+digest. Pi Runtime owns the browser package and browser TCB version checks. The connector
+loads only the sealed extension for these commands using Pi's explicit `--extension`
+flag and disables ambient extension discovery. New browser-credential dispatches require
 `browser_credential_env_read_v1`; they never treat the older capability as
 equivalent. The retired `browser_credential_ref_fill_v1` claim is decode-only.
 Commands carrying credential refs are routed only by their exact required
@@ -117,7 +119,7 @@ The publish workflow runs on pushes that change Connector package inputs. `maste
 
 ## Pi plugin ownership boundary
 
-`pi-cli-runtime` owns Pi plugin installation, versions, package resolution, and configuration. The connector must only start Pi, deliver a command, manage its process lifecycle, and return its result. Do not add Pi-plugin version/digest/config admission checks to connector registration, heartbeat, or ordinary command dispatch. Credential capabilities are the narrow exceptions: the legacy private transaction attests its package manifest and TCB, while `browser_credential_env_read_v1` attests the runner-owned extension entrypoint. An absent or unexpected extension must remove the corresponding capability before dispatch. Other plugin failures remain task execution evidence, not connector admission decisions.
+The `pi-agent` repository owns plugin installation, dependency versions, package resolution, and build validation for `pi-cli-runtime`. The connector passes the Company browser profile through `AMASTER_BROWSER_SESSION_USER_DATA_DIR`; governed browser sessions use their managed profile instead. Do not add Pi package version or digest admission checks to Connector registration, heartbeat, or readiness. Credential capabilities check their Connector-owned runtime extension: the private transaction checks its sealed extension digest, while `browser_credential_env_read_v1` checks its extension entrypoint. An absent or unexpected extension must remove the corresponding capability before dispatch. Other plugin failures remain task execution evidence, not Connector admission decisions.
 
 - `dist/amaster-runtime.mjs`: configuration, pairing, workspace, diagnostics, and daemon lifecycle CLI.
 - `dist/amaster-runtime-daemon.mjs`: standalone daemon bundle for connector registration, heartbeat, command execution, and result ingestion.
@@ -241,10 +243,25 @@ CAS revision. Both modes use the same ownership manifest and byte-ingest path.
 Pi JSON mode can also repeat a cumulative `message` snapshot beside each
 incremental `message_update`. The daemon compacts only that redundant snapshot
 from its retained parse/result buffer while preserving the delta, terminal
-events, live logs, and tool-argument guard input. Output telemetry reports both
-`rawOutputBytes` and `retainedOutputBytes` plus `retentionCompactedBytes`; flood
-limits continue to use raw bytes, so retention compaction never hides transport
-pressure or weakens the 50 MiB safety boundary.
+events, live logs, and tool-argument guard input. For Pi stdout,
+`AMASTER_EXECUTOR_MAX_OUTPUT_BYTES` (50 MiB by default) limits the compacted,
+retained stream. A separate raw stdout safety ceiling is eight times that
+limit, capped at 512 MiB; stderr and other executors still use the configured
+raw-byte limit. Above a configured 512 MiB retained limit, the raw safety
+ceiling can stop the process first. The command result's `outputFlood.basis`
+distinguishes `retained` from `raw`, and telemetry reports both limits and byte counts.
+The raw ceiling, timeout, memory limit, and tool-argument guard remain active
+when Pi emits large redundant JSONL snapshots.
+
+If a Pi assistant message ends at `length` with only thinking content and no
+text or tool call, the daemon permits Pi's next generation so it can use its
+built-in recovery when eligible. A second such message in the same run stops
+the run; an unrecovered first message is classified when the process settles.
+It returns `pi_reasoning_output_exhausted` with token counts and content block
+types, never the thinking text. `outputTelemetry.piGenerationSummary` records
+delta counts/bytes by type, the sum of completed assistant messages' output
+tokens, and length-stop counts. These are diagnostic observations; use provider billing
+records for authoritative usage.
 
 ## Pi terminal cleanup outcome
 

package/dist/amaster-runtime-daemon/capability-registry.mjs

@@ -24,15 +24,9 @@ export const BUILD_SUPPORTED_CAPABILITIES = Object.freeze([
   "mirrorx_initialization_completion_v1",
   "native_session_checkpoint_v1",
   "pi_web_public_search_v1",
-  "pi_web_public_fetch_v1",
 ]);
 
 const DYNAMIC_READINESS = Object.freeze({
-  pi_web_public_fetch_v1: {
-    reasonCode: "pi_web_fetch_extension_unavailable",
-    ready: (input) => input.executors.some((executor) => executor.kind === "pi")
-      && input.piWebFetchReady === true,
-  },
   pi_web_public_search_v1: {
     reasonCode: "pi_web_search_extension_unavailable",
     ready: (input) => input.executors.some((executor) => executor.kind === "pi")
@@ -52,15 +46,8 @@ const DYNAMIC_READINESS = Object.freeze({
   },
   browser_credential_auth_transaction_v1: {
     reasonCode: "browser_credential_auth_runtime_incomplete",
-    ready: (input) => {
-      const readiness = input.browserCredentialAuth;
-      return input.executors.some((executor) => executor.kind === "pi")
-        && readiness?.privateChannel === true
-        && readiness?.executorClient === true
-        && readiness?.sealedGate === true
-        && readiness?.atomicTransaction === true
-        && readiness?.trustedProfileInjection === true;
-    },
+    ready: (input) => input.executors.some((executor) => executor.kind === "pi")
+      && input.browserCredentialAuth?.extension === true,
   },
   native_session_checkpoint_v1: {
     reasonCode: "managed_pi_checkpoint_required",