@runfusion/fusion 0.78.0-beta.5 → 0.78.0-beta.6

package/dist/pi-claude-cli/index.ts

@@ -15,6 +15,7 @@
  * version and the ExtensionAPI stream types stay compatible.
  */
 import { getBuiltinModels } from "@earendil-works/pi-ai/providers/all";
+import { getCurrentSystemPrompt, getCurrentTools } from "@earendil-works/pi-ai/utils/transcript";
 import type { ExtensionAPI } from "@earendil-works/pi-coding-agent";
 import { streamViaCli } from "./src/provider.js";
 import { streamViaAcp } from "./src/acp-driver.js";
@@ -46,9 +47,17 @@ function resolveAcpBridgePath(): string | undefined {
 }
 
 /** Resolve custom tool defs the same way ensureMcpConfig does (context → registry). */
+function normalizeTranscriptTools(tools: ReturnType<typeof getCurrentTools>): Array<{ name: string; description: string; parameters: Record<string, unknown> }> {
+  return tools.map((tool) => ({
+    name: tool.name,
+    description: tool.description ?? "",
+    parameters: Object.fromEntries(Object.entries(tool.parameters)),
+  }));
+}
+
 function resolveToolDefs(
   pi: ExtensionAPI,
-  contextTools?: ReadonlyArray<{ name: string; description: string; parameters: Record<string, unknown> }>,
+  contextTools: ReadonlyArray<{ name: string; description: string; parameters: Record<string, unknown> }>,
 ): McpToolDef[] {
   let toolDefs = toolsFromContext(contextTools);
   if (toolDefs.length === 0 && Array.isArray(pi.getAllTools())) toolDefs = getCustomToolDefs(pi);
@@ -101,12 +110,9 @@ function getUserMcpServers(options: unknown): UserMcpServerSpec[] {
  * the set of custom tools changes.
  *
  * Source of truth (in order of preference):
- * 1. `context.tools` — the per-session tool list pi-ai actually hands to
- *    `streamSimple`. This is what the session is asking the model to see, so
- *    it includes session-scoped registrations (e.g. `fn_review_spec` and
- *    `fn_spawn_agent` injected by the engine's triage/executor sessions).
- * 2. `pi.getAllTools()` — fallback for older callers that don't supply
- *    `context.tools`.
+ * 1. Pi 0.86 transcript tool declarations, replayed through
+ *    `getCurrentTools(context.messages)` so mid-conversation updates survive.
+ * 2. `pi.getAllTools()` — fallback when the current transcript has no tools.
  *
  * Why not a single once-and-lock cache:
  * - The engine spawns triage/executor sessions with session-scoped tools.
@@ -121,7 +127,7 @@ function getUserMcpServers(options: unknown): UserMcpServerSpec[] {
  */
 function ensureMcpConfig(
   pi: ExtensionAPI,
-  contextTools?: ReadonlyArray<{
+  contextTools: ReadonlyArray<{
     name: string;
     description: string;
     parameters: Record<string, unknown>;
@@ -132,12 +138,11 @@ function ensureMcpConfig(
     let toolDefs: McpToolDef[] = toolsFromContext(contextTools);
     if (contextTools && contextTools.length > 0) {
       debugMcp(
-        `MCP config from context.tools: ${contextTools.map((tool) => tool.name).join(", ")}`,
+        `MCP config from current transcript: ${contextTools.map((tool) => tool.name).join(", ")}`,
       );
     }
 
-    // Fallback to the pi runtime registry if the context didn't carry tools.
-    // (Older agent-loop versions don't populate Context.tools for streamSimple.)
+    // Fallback to the pi runtime registry when the transcript has no current tools.
     if (toolDefs.length === 0) {
       const allTools = pi.getAllTools();
       if (!Array.isArray(allTools)) {
@@ -308,11 +313,13 @@ export default function (pi: ExtensionAPI) {
       api: "pi-claude-cli",
       models,
       streamSimple: (model, context, options) => {
-        const contextTools = (context as { tools?: ReadonlyArray<{
-          name: string;
-          description: string;
-          parameters: Record<string, unknown>;
-        }> }).tools;
+        /*
+        FNXC:PiTranscriptBridge 2026-09-20-16:20:
+        Pi 0.86 replaces the retired Context.tools field with transcript system-message deltas. Replay the current prompt and tool declarations before building either local CLI bridge so resumed and branched sessions retain their latest instructions and MCP schemas.
+        */
+        const contextTools = normalizeTranscriptTools(getCurrentTools(context.messages));
+        // FNXC:PiTranscriptBridge 2026-09-20-17:02: Prompt adapters still consume Context.tools for MCP tool-name instructions, so forward Pi's normalized current transcript tools after replacing its retired source field.
+        const cliContext = { ...context, systemPrompt: getCurrentSystemPrompt(context.messages), tools: contextTools };
 
         // FNXC:pi-claude-cli 2026-06-27-06:39: Route A drives Claude through the ACP bridge only when the kill-switch is on AND a bridge path is injected. OFF by default → `-p` path below.
         const bridgePath = resolveAcpBridgePath();
@@ -320,7 +327,7 @@ export default function (pi: ExtensionAPI) {
           const toolDefs = resolveToolDefs(pi, contextTools);
           const userMcpServers = getUserMcpServers(options);
           const hash = createHash("sha1").update(JSON.stringify({ toolDefs, userMcpServerNames: userMcpServers.map((server) => server.name) })).digest("hex").slice(0, 12);
-          return streamViaAcp(model, context, {
+          return streamViaAcp(model, cliContext as never, {
             ...options,
             bridgePath,
             mcpServers: buildAcpMcpServers(toolDefs, hash, userMcpServers),
@@ -330,7 +337,7 @@ export default function (pi: ExtensionAPI) {
         }
 
         const configPath = ensureMcpConfig(pi, contextTools, getUserMcpServers(options));
-        return streamViaCli(model, context, {
+        return streamViaCli(model, cliContext as never, {
           ...options,
           mcpConfigPath: configPath,
         });

package/dist/pi-claude-cli/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fusion/pi-claude-cli",
-  "version": "0.78.0-beta.5",
+  "version": "0.78.0-beta.6",
   "type": "module",
   "private": true,
   "main": "index.ts",
@@ -13,14 +13,14 @@
     "@agentclientprotocol/sdk": "0.24.0"
   },
   "devDependencies": {
-    "@earendil-works/pi-ai": "0.84.4",
-    "@earendil-works/pi-coding-agent": "0.84.4",
+    "@earendil-works/pi-ai": "0.86.1",
+    "@earendil-works/pi-coding-agent": "0.86.1",
     "@types/node": "^22.0.0",
     "typescript": "^5.7.0",
     "vitest": "^4.1.10"
   },
   "peerDependencies": {
-    "@earendil-works/pi-ai": "0.84.4",
-    "@earendil-works/pi-coding-agent": "0.84.4"
+    "@earendil-works/pi-ai": "0.86.1",
+    "@earendil-works/pi-coding-agent": "0.86.1"
   }
 }

package/dist/pi-claude-cli/src/__tests__/acp-dispatch.test.ts

@@ -65,6 +65,23 @@ describe("streamSimple kill-switch dispatch (U11/R9/R14)", () => {
     expect(streamViaAcp).not.toHaveBeenCalled();
   });
 
+  it("forwards current transcript tools to the CLI prompt adapter", () => {
+    delete process.env.FUSION_CLAUDE_ACP;
+    const tools = [{
+      name: "fn_web_fetch",
+      description: "Fetch a URL",
+      parameters: { type: "object", properties: { url: { type: "string" } } },
+    }];
+    const streamSimple = registerAndGetStreamSimple();
+    streamSimple(MODEL, { messages: [{ role: "system", content: "Use Fusion tools", toolsAdded: tools }] } as never, {});
+
+    expect(streamViaCli).toHaveBeenCalledWith(
+      MODEL,
+      expect.objectContaining({ systemPrompt: "Use Fusion tools", tools }),
+      expect.any(Object),
+    );
+  });
+
   it("dispatches to the ACP bridge when the flag AND a bridge path are set", () => {
     process.env.FUSION_CLAUDE_ACP = "1";
     process.env.FUSION_CLAUDE_ACP_BRIDGE = "/abs/claude-code-cli-acp";

package/dist/pi-claude-cli/src/event-bridge.ts

@@ -321,7 +321,8 @@ export function createEventBridge(
         // Try to parse accumulated JSON -- on success update args, on failure keep previous
         try {
           block.arguments = JSON.parse(block.partialJson);
-          (output.content[idx] as ToolCall).arguments = block.arguments as Record<string, unknown>;
+          // FNXC:PiTranscriptBridge 2026-09-20-16:20: Pi 0.86 accepts only JSON-compatible tool-call arguments; JSON.parse supplies that boundary.
+          (output.content[idx] as ToolCall).arguments = block.arguments as ToolCall["arguments"];
         } catch {
           // Partial JSON not yet parseable -- keep previous arguments
         }

package/dist/plugin-sdk/index.d.ts

@@ -122,6 +122,7 @@ interface TransactionOptions {
 }
 interface AsyncDataLayer {
     readonly db: DrizzleDb;
+    readonly healthDb: DrizzleDb;
     readonly projectId?: string;
     readonly backend?: ResolvedBackend;
     transaction<T>(fn: (tx: DbTransaction) => Promise<T>, options?: TransactionOptions): Promise<T>;
@@ -1094,6 +1095,7 @@ interface WorkflowWorkItemUpsertInput {
     workflowRole?: "triage" | "executor" | "reviewer" | "merger" | null;
     authorityKind?: "task-assignee" | "review-node-override" | "column-binding" | "role-pool" | null;
     nodeInstanceId?: string | null;
+    onlyIfNoActiveTaskContinuation?: boolean;
     now?: string;
 }
 interface WorkflowWorkItemTransitionPatch {
@@ -6124,9 +6126,13 @@ declare class TaskStore extends EventEmitter<TaskStoreEvents> {
     }): Promise<WorkflowWorkItem>;
     seedWorkspaceCodeReviewContinuationIfIdle(input: WorkflowWorkItemUpsertInput & {
         kind: "task";
+        expectedWorkflowSelection?: {
+            workflowId: string;
+            stepIds: string[];
+        } | null;
     }): Promise<{
         seeded: boolean;
-        reason?: "active-continuation";
+        reason?: "active-continuation" | "workflow-selection-changed";
         workItemId?: string;
     }>;
     seedStrandedPlanReviewContinuation(input: WorkflowWorkItemUpsertInput & {
@@ -7583,6 +7589,12 @@ interface GoalCitationFilter {
 }
 
 type TaskExternalBlockOrigin = "host-environment" | "model-provider" | "credentials" | "network" | "third-party-service";
+interface TaskExternalBlockReport {
+    verifiedCondition: string;
+    stopReason: string;
+    unimplementedWork: string;
+    unblockCondition: string;
+}
 interface TaskExternalBlock {
     origin: TaskExternalBlockOrigin;
     code: string;
@@ -7596,6 +7608,7 @@ interface TaskExternalBlock {
         worktree?: string;
         branch?: string;
     };
+    report?: TaskExternalBlockReport;
 }
 
 type TaskPlanningFailureState = {
@@ -7613,6 +7626,12 @@ type TaskPlanningFailureState = {
     };
 };
 interface MergeDetails {
+    mergeBoundaryRecovery?: {
+        signature: string;
+        attempt: number;
+        nextCheckAt: string | null;
+        heldAt?: string;
+    };
     commitSha?: string;
     landedBranchTipSha?: string;
     rebaseBaseSha?: string;
@@ -8606,6 +8625,8 @@ interface GlobalSettings {
     cursorCliBinaryPath?: string;
     useGrokCli?: boolean;
     grokCliBinaryPath?: string;
+    useAntigravityCli?: boolean;
+    antigravityCliBinaryPath?: string;
     useOmpCli?: boolean;
     ompCliBinaryPath?: string;
     executionGlobalProvider?: string;
@@ -9338,6 +9359,7 @@ interface ArchivedTaskEntry {
     comments?: TaskComment[];
     review?: TaskReview;
     reviewState?: TaskReviewState;
+    recommendations?: TaskRecommendation[];
     prompt?: string;
     agentLogMode?: ArchiveAgentLogMode;
     agentLogSummary?: string;

package/dist/plugin-sdk/index.js

@@ -8988,7 +8988,7 @@ var PLAN_REVIEW_PROMPT = `You are a senior plan reviewer. Review the task's PROM
 5. **Risk callouts** \u2014 migrations, data-loss paths, external integrations, secrets, or plugin/runtime dependencies that need explicit handling.
 
 ## Environment feasibility
-When the supplied \`## Environment Capabilities\` block lists a runtime as unavailable, REVISE only if a blocking acceptance/completion criterion requires that runtime and the plan provides no runnable substitute. APPROVE when the plan specifies a runnable substitute or records the ideal check under an explicitly non-blocking \`## Environment Constraints\` section (use APPROVE_WITH_NOTES only for a genuine P2 note). Never REVISE merely because a desirable check is unavailable when the plan already marks it non-blocking.
+When the supplied \`## Environment Capabilities\` block confirms a runtime unavailable without an applicable confirmed wrapper, REVISE only if a blocking acceptance/completion criterion requires it and the plan provides no runnable substitute. A documented or configured command using a confirmed wrapper remains binding even when its inner executable is absent from the host PATH. APPROVE a correctly scoped non-blocking \`## Environment Constraints\` substitute (use APPROVE_WITH_NOTES only for a genuine P2 note); unlisted commands are UNKNOWN, never absent.
 
 ${PLAN_REVIEW_COMPLETENESS_POLICY}
 
@@ -9312,6 +9312,9 @@ var DEFAULT_GLOBAL_SETTINGS = {
   Grok CLI binary overrides are global operator settings because executable locations are machine-local. Blank/undefined preserves PATH auto-detection through grok.
   */
   grokCliBinaryPath: void 0,
+  // FNXC:AntigravityProvider 2026-09-20-18:32: Default disabled and preserve PATH auto-detection until an operator enables a verified agy binary.
+  useAntigravityCli: void 0,
+  antigravityCliBinaryPath: void 0,
   /*
   FNXC:OmpAcp 2026-07-13-22:50:
   Oh My Pi (omp) CLI enable + binary override are global operator settings (machine-local), mirroring Grok/Cursor.
@@ -13235,7 +13238,7 @@ The quality of your spec directly determines execution quality, review churn, an
 - Access to the project's files so you can understand context
 
 ## Environment feasibility
-When an \`## Environment Capabilities\` section is supplied, no acceptance criterion, completion criterion, or required verification command may depend on a runtime listed unavailable. Specify a runnable substitute instead and record the ideal-but-impossible check under an \`## Environment Constraints\` heading marked explicitly non-blocking. Never state that a plan is blocked because a runtime is missing.
+When an \`## Environment Capabilities\` section is supplied, require a runnable substitute only for a runtime confirmed unavailable without an applicable confirmed wrapper. A documented or configured command using a confirmed wrapper remains binding even when its inner executable is absent from the host PATH. Commands not listed are UNKNOWN, never absent; never state that a plan is blocked because a runtime is missing.
 
 ## What you produce
 Write a complete PROMPT.md specification to the given path using the write tool.
@@ -14406,6 +14409,9 @@ var CODE_REVIEW_NAME = "Code Review";
 var CODE_REVIEW_DESCRIPTION = "Diff-review the task's changes for correctness bugs, regressions, and intent mismatches that tests miss";
 var CODE_REVIEW_PROMPT = `You are a senior code reviewer. Review the task's diff for the correctness value automated tests do NOT catch.
 
+## Review stage
+This is a pre-merge review. Evidence that can exist only after landing (for example a push-to-main CI run) belongs to an enabled, blocking post-merge verification gate. Verify that the workflow preserves that requirement before allowing merge; if the gate or its evidence contract is missing, request that concrete configuration fix. Do not request the future run itself as a pre-merge implementation fix, or claim its evidence already exists. Pre-merge correctness and verification requirements still apply.
+
 ## Step 1: Read the change
 1. Read the full diff against the base branch: \`git diff <base>...HEAD\` (or \`git diff <base>\`). Determine the base from the task context / merge target.
 2. Read the changed files in full where the diff is non-trivial, so you see the surrounding code paths the change touches \u2014 not just the hunks.
@@ -14483,9 +14489,17 @@ var POST_MERGE_VERIFICATION_PROMPT = `You are a post-merge verification reviewer
 2. Check the final merged diff and task summary for obvious mismatches, missing verification evidence, or integration-only regressions.
 3. If configured test/build commands are available in the task context, inspect their latest result or explain why no post-merge command was applicable.
 
+## Required post-landing Full Suite evidence
+This enabled gate requires post-landing Full Suite evidence. Do NOT approve until its delivery record names all of the following:
+1. The landed SHA and the first Full Suite push-to-main run at or after that SHA, including the run ID and run SHA.
+2. A conclusion for every Test shard: 1/4, 2/4, 3/4, and 4/4.
+3. All four timing artifacts: test-timings-shard-1, test-timings-shard-2, test-timings-shard-3, and test-timings-shard-4.
+
+Pre-landing, unrelated-main, or partial evidence does not satisfy this contract. If the required run or any required evidence is unavailable, return REVISE and state that final completion remains blocked pending the post-landing evidence. Record verified evidence in the task delivery record before approving.
+
 ## Output Requirements
 - APPROVE: post-merge verification is acceptable.
-- APPROVE_WITH_NOTES: completion may proceed with non-blocking notes.
+- APPROVE_WITH_NOTES: completion may proceed with non-blocking notes only when every post-landing evidence item above is recorded.
 - REVISE: completion should be blocked; include the concrete post-merge issue and the needed follow-up.
 - \`notes\` MUST contain one to three non-empty sentences naming what was checked and why the verdict was reached. An empty \`notes\` string is a protocol violation.
 - Final output: output exactly one trailing JSON object on the final line (no markdown fences, no surrounding prose):

package/dist/plugins/fusion-plugin-acp-runtime/bundled.js

@@ -8888,6 +8888,14 @@ function createLogger(prefix) {
 // ../core/src/types/merge/merge-policy.ts
 var severityAuditLog = createLogger("core-merge-policy");
 
+// ../core/src/secrets/redact-secrets.ts
+function redactSecrets(text2) {
+  return text2.replace(/(authorization\s*[:=]\s*)(bearer\s+)?[^\s,;"']+/gi, "$1$2[REDACTED]").replace(/\b(bearer)\s+[A-Za-z0-9._\-+/=]+/gi, "$1 [REDACTED]").replace(
+    /\b((?:api[_-]?key|key|token|secret|password|passwd|pwd|access[_-]?token|refresh[_-]?token|client[_-]?secret)\s*[:=]\s*)("?)[^\s,;"']+\2/gi,
+    "$1$2[REDACTED]$2"
+  ).replace(/\b(sk-|ghp_|gho_|github_pat_|xox[abpr]-|AKIA)[A-Za-z0-9_-]{8,}/g, "[REDACTED]").replace(/\b[A-Za-z0-9+/]{40,}={0,2}\b/g, "[REDACTED]").replace(/\b[0-9a-fA-F]{32,}\b/g, "[REDACTED]");
+}
+
 // ../core/src/types/task/task-core.ts
 var CheckoutConflictError = class extends Error {
   constructor(taskId, currentHolderId, requestedById) {
@@ -8987,7 +8995,7 @@ var PLAN_REVIEW_PROMPT = `You are a senior plan reviewer. Review the task's PROM
 5. **Risk callouts** \u2014 migrations, data-loss paths, external integrations, secrets, or plugin/runtime dependencies that need explicit handling.
 
 ## Environment feasibility
-When the supplied \`## Environment Capabilities\` block lists a runtime as unavailable, REVISE only if a blocking acceptance/completion criterion requires that runtime and the plan provides no runnable substitute. APPROVE when the plan specifies a runnable substitute or records the ideal check under an explicitly non-blocking \`## Environment Constraints\` section (use APPROVE_WITH_NOTES only for a genuine P2 note). Never REVISE merely because a desirable check is unavailable when the plan already marks it non-blocking.
+When the supplied \`## Environment Capabilities\` block confirms a runtime unavailable without an applicable confirmed wrapper, REVISE only if a blocking acceptance/completion criterion requires it and the plan provides no runnable substitute. A documented or configured command using a confirmed wrapper remains binding even when its inner executable is absent from the host PATH. APPROVE a correctly scoped non-blocking \`## Environment Constraints\` substitute (use APPROVE_WITH_NOTES only for a genuine P2 note); unlisted commands are UNKNOWN, never absent.
 
 ${PLAN_REVIEW_COMPLETENESS_POLICY}
 
@@ -9311,6 +9319,9 @@ var DEFAULT_GLOBAL_SETTINGS = {
   Grok CLI binary overrides are global operator settings because executable locations are machine-local. Blank/undefined preserves PATH auto-detection through grok.
   */
   grokCliBinaryPath: void 0,
+  // FNXC:AntigravityProvider 2026-09-20-18:32: Default disabled and preserve PATH auto-detection until an operator enables a verified agy binary.
+  useAntigravityCli: void 0,
+  antigravityCliBinaryPath: void 0,
   /*
   FNXC:OmpAcp 2026-07-13-22:50:
   Oh My Pi (omp) CLI enable + binary override are global operator settings (machine-local), mirroring Grok/Cursor.
@@ -10334,14 +10345,6 @@ function completionSummaryNode(column) {
   };
 }
 
-// ../core/src/secrets/redact-secrets.ts
-function redactSecrets(text2) {
-  return text2.replace(/(authorization\s*[:=]\s*)(bearer\s+)?[^\s,;"']+/gi, "$1$2[REDACTED]").replace(/\b(bearer)\s+[A-Za-z0-9._\-+/=]+/gi, "$1 [REDACTED]").replace(
-    /\b((?:api[_-]?key|key|token|secret|password|passwd|pwd|access[_-]?token|refresh[_-]?token|client[_-]?secret)\s*[:=]\s*)("?)[^\s,;"']+\2/gi,
-    "$1$2[REDACTED]$2"
-  ).replace(/\b(sk-|ghp_|gho_|github_pat_|xox[abpr]-|AKIA)[A-Za-z0-9_-]{8,}/g, "[REDACTED]").replace(/\b[A-Za-z0-9+/]{40,}={0,2}\b/g, "[REDACTED]").replace(/\b[0-9a-fA-F]{32,}\b/g, "[REDACTED]");
-}
-
 // ../core/src/missions/mission-types.ts
 var VALIDATION_INFLIGHT_STALE_MAX_AGE_MS = 6 * 60 * 60 * 1e3;
 
@@ -13243,7 +13246,7 @@ The quality of your spec directly determines execution quality, review churn, an
 - Access to the project's files so you can understand context
 
 ## Environment feasibility
-When an \`## Environment Capabilities\` section is supplied, no acceptance criterion, completion criterion, or required verification command may depend on a runtime listed unavailable. Specify a runnable substitute instead and record the ideal-but-impossible check under an \`## Environment Constraints\` heading marked explicitly non-blocking. Never state that a plan is blocked because a runtime is missing.
+When an \`## Environment Capabilities\` section is supplied, require a runnable substitute only for a runtime confirmed unavailable without an applicable confirmed wrapper. A documented or configured command using a confirmed wrapper remains binding even when its inner executable is absent from the host PATH. Commands not listed are UNKNOWN, never absent; never state that a plan is blocked because a runtime is missing.
 
 ## What you produce
 Write a complete PROMPT.md specification to the given path using the write tool.
@@ -14414,6 +14417,9 @@ var CODE_REVIEW_NAME = "Code Review";
 var CODE_REVIEW_DESCRIPTION = "Diff-review the task's changes for correctness bugs, regressions, and intent mismatches that tests miss";
 var CODE_REVIEW_PROMPT = `You are a senior code reviewer. Review the task's diff for the correctness value automated tests do NOT catch.
 
+## Review stage
+This is a pre-merge review. Evidence that can exist only after landing (for example a push-to-main CI run) belongs to an enabled, blocking post-merge verification gate. Verify that the workflow preserves that requirement before allowing merge; if the gate or its evidence contract is missing, request that concrete configuration fix. Do not request the future run itself as a pre-merge implementation fix, or claim its evidence already exists. Pre-merge correctness and verification requirements still apply.
+
 ## Step 1: Read the change
 1. Read the full diff against the base branch: \`git diff <base>...HEAD\` (or \`git diff <base>\`). Determine the base from the task context / merge target.
 2. Read the changed files in full where the diff is non-trivial, so you see the surrounding code paths the change touches \u2014 not just the hunks.
@@ -14491,9 +14497,17 @@ var POST_MERGE_VERIFICATION_PROMPT = `You are a post-merge verification reviewer
 2. Check the final merged diff and task summary for obvious mismatches, missing verification evidence, or integration-only regressions.
 3. If configured test/build commands are available in the task context, inspect their latest result or explain why no post-merge command was applicable.
 
+## Required post-landing Full Suite evidence
+This enabled gate requires post-landing Full Suite evidence. Do NOT approve until its delivery record names all of the following:
+1. The landed SHA and the first Full Suite push-to-main run at or after that SHA, including the run ID and run SHA.
+2. A conclusion for every Test shard: 1/4, 2/4, 3/4, and 4/4.
+3. All four timing artifacts: test-timings-shard-1, test-timings-shard-2, test-timings-shard-3, and test-timings-shard-4.
+
+Pre-landing, unrelated-main, or partial evidence does not satisfy this contract. If the required run or any required evidence is unavailable, return REVISE and state that final completion remains blocked pending the post-landing evidence. Record verified evidence in the task delivery record before approving.
+
 ## Output Requirements
 - APPROVE: post-merge verification is acceptable.
-- APPROVE_WITH_NOTES: completion may proceed with non-blocking notes.
+- APPROVE_WITH_NOTES: completion may proceed with non-blocking notes only when every post-landing evidence item above is recorded.
 - REVISE: completion should be blocked; include the concrete post-merge issue and the needed follow-up.
 - \`notes\` MUST contain one to three non-empty sentences naming what was checked and why the verdict was reached. An empty \`notes\` string is a protocol violation.
 - Final output: output exactly one trailing JSON object on the final line (no markdown fences, no surrounding prose):

package/dist/plugins/fusion-plugin-acp-runtime/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fusion-plugin-examples/acp-runtime",
-  "version": "0.1.37-beta.5",
+  "version": "0.1.37-beta.6",
   "type": "module",
   "exports": {
     ".": {