@amaster.ai/employee-runtime-connector 0.1.1-beta.253 → 0.1.1-beta.255

package/README.md

@@ -85,7 +85,30 @@ For Server-dispatched Codex `run` and `wakeup` commands, the effective model com
 
 For admitted Pi runs, the daemon compiles source-repository `AGENTS.md` and `AGENTS.override.md` topology into one root `AGENTS.md` with explicit relative scopes, same-scope override semantics, and a higher-authority MirrorX platform block. Governed Pi preserves operator-configured user extensions and tools, disables ambient skill and context-file discovery, and injects that exact compiled file through a run-owned final-system-prompt extension. `pi-mcp-adapter` normally merges the operator's user-level `mcp.json` with the run-owned workspace `.pi/mcp.json`; the workspace definition wins on a same-name server, and only environment placeholders referenced by preserved user MCP definitions are granted to the child. Governed MCP tools remain fail-closed: the daemon requires their exact catalog and schemas while accepting additional Pi-native or user-extension tools, including the adapter proxy when a user MCP needs it. Run-exit closure applies the same rule to its two required MirrorX tools as a schema-bound subset instead of rejecting the ambient user tool surface. When the operator-owned Pi settings declare `@amaster.ai/pi-telemetry`, the daemon verifies that package's immutable identity and preserves the authoritative runtime run id for trace correlation while Pi loads it normally from the shared settings. A last-ordered `before_provider_request` hook then validates every provider call, including later calls after tool results: exactly one system message contains the compiled instructions, visible role-skill metadata and the attested active tool contract match their prior attestations, and the complete serialized input fits the context window. It does not override the active model's output limit or inject provider `max_tokens`, `max_completion_tokens`, or `max_output_tokens`; no `modelMaxOutputTokens` substitute exists. Each call appends metadata-only hashes and sizes to a bounded chained receipt; a missing, broken, or oversized chain fails the run.
 
-Pi 0.80.10's internal compaction summarizer calls the provider outside `before_provider_request`. The Enabled profile therefore records and cancels every `session_before_compact` attempt and fails immediately if `session_compact` is nevertheless observed. No model-generated compaction summary is accepted until that provider path has equivalent final-context attestation. The Server also enumerates Pi and Codex as the only supported governed executors at configuration and heartbeat dispatch boundaries; missing or unknown executor kinds fail closed.
+Pi 0.80.10's internal compaction summarizer calls the provider outside `before_provider_request`. The Enabled profile therefore records and cancels every `session_before_compact` attempt and fails immediately if `session_compact` is nevertheless observed. No model-generated compaction summary is accepted until that provider path has equivalent final-context attestation. The Server enumerates Pi, Codex, and the gated CodeBuddy driver as the only supported governed executors at configuration and heartbeat dispatch boundaries; missing or unknown executor kinds fail closed.
+
+## WorkBuddy Host (CodeBuddy engine)
+
+The optional `codebuddy` executor exposes the same common governed task contract as
+Codex, while remaining deliberately narrower than the WorkBuddy desktop product.
+It does not expose WorkBuddy experts, projects, Office integrations, marketplace
+connectors, or Pi's `final_model_context_attestation_v1`. The connector creates a
+private per-run CodeBuddy home, supplies one strict MirrorX MCP definition, uses an
+exact native-tool allowlist, and preserves only an authority-bound native session
+rollout. It never inherits the user's ordinary `.codebuddy` or WorkBuddy profile.
+
+This executor is off by default. Enable discovery with
+`AMASTER_ENABLE_CODEBUDDY_EXECUTOR=true`. `AMASTER_CODEBUDDY_COMMAND` can select an
+explicit CLI; on macOS the gated discovery path can also find the CLI bundled in
+`/Applications/WorkBuddy.app`. The Server task-session snapshot owns the model for
+current commands; `AMASTER_CODEBUDDY_MODEL` is only a compatibility fallback for
+older commands without that snapshot. The daemon environment or a Server-issued
+command environment must provide exactly one of `CODEBUDDY_API_KEY` or
+`CODEBUDDY_AUTH_TOKEN`; ordinary host login state is not a credential source.
+Command-scoped values override same-name daemon values. Provider routing may additionally use the supported
+`CODEBUDDY_INTERNET_ENVIRONMENT`, `CODEBUDDY_BASE_URL`, or proxy variables. Secret
+values remain run-scoped and must never be placed in arguments, logs, connector
+metadata, or committed configuration.
 
 This is an intentional compatibility break for the not-yet-public context-governance contract. There is no historical command migration, dual-read, or fallback from a new Server-issued envelope to an unproved executor path.