@amaster.ai/employee-runtime-connector 0.1.1-beta.3 → 0.1.1-beta.30

package/README.md

@@ -13,7 +13,7 @@ For production images, install an exact version and invoke the package bin:
 ```sh
 npm install --omit=dev --prefix /opt/pi-cli-runtime @amaster.ai/employee-runtime-connector@0.1.0
 /opt/pi-cli-runtime/node_modules/.bin/amaster-runtime setup https://employee.example.com \
-  --capabilities remote_registration,heartbeat,executor_discovery,workspace_binding,run_wakeup,model_call,run_cancel,run_terminate,logs_cost_workspace_status
+  --capabilities remote_registration,heartbeat,executor_discovery,workspace_binding,run_wakeup,model_call,model_call_output_contract_v1,run_cancel,run_terminate,logs_cost_workspace_status
 /opt/pi-cli-runtime/node_modules/.bin/amaster-runtime daemon start --foreground
 ```
 
@@ -32,6 +32,47 @@ The source of truth lives under this package's `src/` directory. The package bui
 
 Runtime code belongs in the container image. Persist only connector state, the result outbox, and workspaces under the configured state directory.
 
+## Contracted Pi model calls
+
+Pi `model_call` commands with `model_call_output_contract_v1` keep provider and
+model selection paired with the output ceiling. Command target fields have the
+highest precedence, followed by `AMASTER_PI_PROVIDER` / `AMASTER_PI_MODEL`, then
+the Pi profile's `defaultProvider` / `defaultModel`. Each selected precedence
+layer must be a complete provider/model pair: a partial command or runtime
+override fails closed instead of silently falling through to a lower-precedence
+default. The daemon copies only the normalized default pair into the isolated
+one-shot profile, validates that the resolved model exists, applies
+`maxOutputTokens` to that exact model, and records the resolved target and source
+in command-result diagnostics. Missing or unknown targets also fail closed
+before Pi is spawned.
+
+## Pi tool-argument transport guard
+
+`AMASTER_PI_TOOL_ARGUMENT_GUARD_MODE` defaults to `shadow`; supported values are
+`off`, `shadow`, and `enforce`. Shadow records metadata-only matches while the
+single-incident thresholds are calibrated. Promote deliberately to `enforce`
+after reviewing near misses and false positives; use `off` as the emergency
+rollback. The enforce signature
+requires at least 8 MiB transported, at most 512 KiB materialized, and at least
+16x amplification before `tool_execution_start`. Replay ratio is telemetry,
+not a kill prerequisite. Threshold overrides are available through the
+`AMASTER_PI_TOOL_ARGUMENT_*` environment variables, but production changes
+must be based on shadow telemetry and false-positive review.
+
+An enforced stop returns `pi_tool_argument_stream_amplification` with
+`retryable=false` and recommends
+`upsert_document_revision_from_workspace_file`. The command result keeps only
+byte counts, ratios, event/tool identity, thresholds, and near-miss distances;
+it omits the inline argument body.
+
+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.
+
 ## Pi terminal cleanup outcome
 
 Pi execution uses three separate evidence layers: