@amaster.ai/employee-runtime-connector 0.1.1-beta.331 → 0.1.1-beta.333

package/README.md

@@ -79,13 +79,11 @@ Runtime code belongs in the container image. Persist only connector state, the r
 
 ## Enabled context-governance admission
 
-The Server requires `final_model_context_attestation_v1` for governed Pi runs because that path disables ambient context discovery and injects a run-owned compiled instruction bundle. This is a Pi delivery contract, not a connector-wide requirement: an explicitly selected self-hosted Codex runtime continues through its own Runtime Actions V2 and native-session contracts and cannot borrow the Pi attestation claim. Adding the same final-context guarantee to another executor requires executor-specific proof for scoped project-instruction semantics, the normalized final active tool schemas, the selected model's context window, automatically visible skill metadata, and resumed-session history.
+The Server admits governed Pi through the shared context-envelope and managed-project-instruction capabilities. The retired `final_model_context_attestation_v1` capability is no longer advertised or required.
 
 For Server-dispatched Codex `run` and `wakeup` commands, the effective model comes from the command's `mirrorxRuntimeConnectorTaskSessionV1.configuredModel` snapshot and is passed to Codex with `--model`. `AMASTER_CODEX_MODEL` is only a compatibility fallback for older commands that do not contain that snapshot; it does not override a Server-issued model or an explicit Server-issued `null` model. A malformed or identity-mismatched snapshot fails closed with `codex_model_authority_invalid`. Its non-empty `taskKey` is an opaque Server task-session identity and is not required to equal the Issue id; the current adapter binding intentionally accepts only `codex_local`.
 
-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 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.
+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 project-instruction 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. The daemon projects the Server-issued tool catalog into run-owned MCP config and cache before spawn without revalidating that platform-owned surface. Project instructions and promoted skills use `before_agent_start` only to inject frozen content; governed tool inputs use `tool_call` for trust-boundary schema validation. No MirrorX extension validates platform-owned context or tool surfaces during execution, and no MirrorX extension uses `session_start`, `before_provider_request`, `session_before_compact`, or `session_compact`. Pi owns provider payload construction, history and native compaction. Runtime Actions, artifact receipts, completion closure and cost telemetry remain the post-run authorities.
 
 ## WorkBuddy Host (CodeBuddy engine)
 
@@ -93,7 +91,7 @@ The optional `codebuddy` executor participates in the same governed task lifecyc
 as Codex, while its local execution surface remains deliberately narrower than both
 Codex and 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
+connectors. The connector creates a
 private per-run CodeBuddy home, supplies one strict MirrorX MCP definition, uses an
 exact tool allowlist, exposes the governed namespace directly with
 `NoDefer(mcp__amaster__*)`, and preserves only an authority-bound native session

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

@@ -8,7 +8,6 @@ export const BUILD_SUPPORTED_CAPABILITIES = Object.freeze([
   "task_context_v2",
   "managed_project_instructions_v1",
   "artifact_template_catalog_v1",
-  "final_model_context_attestation_v1",
   "runtime_actions_v2",
   "runtime_artifact_live_manifest_v1",
   "continue_task_v1",
@@ -57,20 +56,6 @@ const DYNAMIC_READINESS = Object.freeze({
         && catalog.targetDir === input.runtimeTemplatesRoot;
     },
   },
-  final_model_context_attestation_v1: {
-    reasonCode: (input) => input.runnerKind === "desktop_delegated"
-      && input.executors.some((executor) => executor.kind === "pi")
-      ? input.piFinalContextAttestation?.reasonCode ?? "desktop_pi_attestation_runtime_not_ready"
-      : "attested_pi_executor_required",
-    ready: (input) => input.executors.some((executor) => executor.kind === "pi")
-      && (
-        input.runnerKind === "cloud_managed"
-        || (
-          input.runnerKind === "desktop_delegated"
-          && input.piFinalContextAttestation?.ready === true
-        )
-      ),
-  },
 });
 
 function uniqueStrings(values) {