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

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

@@ -8987,7 +8987,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 +9311,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):
@@ -20054,10 +20068,28 @@ function resolveCliSettings(settings) {
 // ../../plugins/fusion-plugin-droid-runtime/src/provider.ts
 import { createInterface } from "node:readline";
 
-// ../../node_modules/.pnpm/@earendil-works+pi-ai@0.84.4_@modelcontextprotocol+sdk@1.28.0_zod@4.4.3__ws@8.21.3_zod@4.4.3/node_modules/@earendil-works/pi-ai/dist/utils/event-stream.js
+// ../../node_modules/.pnpm/@earendil-works+pi-ai@0.86.1_@modelcontextprotocol+sdk@1.28.0_zod@4.4.3__ws@8.21.3_zod@4.4.3/node_modules/@earendil-works/pi-ai/dist/utils/event-stream.js
+var FifoQueue = class {
+  incoming = [];
+  outgoing = [];
+  get length() {
+    return this.incoming.length + this.outgoing.length;
+  }
+  enqueue(value) {
+    this.incoming.push(value);
+  }
+  dequeue() {
+    if (this.outgoing.length === 0) {
+      while (this.incoming.length > 0) {
+        this.outgoing.push(this.incoming.pop());
+      }
+    }
+    return this.outgoing.pop();
+  }
+};
 var EventStream = class {
-  queue = [];
-  waiting = [];
+  queue = new FifoQueue();
+  waiting = new FifoQueue();
   done = false;
   finalResultPromise;
   resolveFinalResult;
@@ -20077,11 +20109,11 @@ var EventStream = class {
       this.done = true;
       this.resolveFinalResult(this.extractResult(event));
     }
-    const waiter = this.waiting.shift();
+    const waiter = this.waiting.dequeue();
     if (waiter) {
       waiter({ value: event, done: false });
     } else {
-      this.queue.push(event);
+      this.queue.enqueue(event);
     }
   }
   end(result) {
@@ -20090,18 +20122,18 @@ var EventStream = class {
       this.resolveFinalResult(result);
     }
     while (this.waiting.length > 0) {
-      const waiter = this.waiting.shift();
+      const waiter = this.waiting.dequeue();
       waiter({ value: void 0, done: true });
     }
   }
   async *[Symbol.asyncIterator]() {
     while (true) {
       if (this.queue.length > 0) {
-        yield this.queue.shift();
+        yield this.queue.dequeue();
       } else if (this.done) {
         return;
       } else {
-        const result = await new Promise((resolve3) => this.waiting.push(resolve3));
+        const result = await new Promise((resolve3) => this.waiting.enqueue(resolve3));
         if (result.done)
           return;
         yield result.value;
@@ -20125,7 +20157,7 @@ var AssistantMessageEventStream = class extends EventStream {
   }
 };
 
-// ../../node_modules/.pnpm/@earendil-works+pi-ai@0.84.4_@modelcontextprotocol+sdk@1.28.0_zod@4.4.3__ws@8.21.3_zod@4.4.3/node_modules/@earendil-works/pi-ai/dist/models.js
+// ../../node_modules/.pnpm/@earendil-works+pi-ai@0.86.1_@modelcontextprotocol+sdk@1.28.0_zod@4.4.3__ws@8.21.3_zod@4.4.3/node_modules/@earendil-works/pi-ai/dist/models.js
 function calculateCost(model, usage) {
   const inputTokens = usage.input + usage.cacheRead + usage.cacheWrite;
   let rates = model.cost;

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

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

package/dist/plugins/fusion-plugin-grok-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-grok-runtime/package.json

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

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

@@ -8990,7 +8990,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}
 
@@ -9314,6 +9314,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.
@@ -13238,7 +13241,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.
@@ -14409,6 +14412,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.
@@ -14486,9 +14492,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-hermes-runtime/package.json

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

package/dist/plugins/fusion-plugin-linear-import/bundled.js

@@ -8987,7 +8987,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 +9311,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-linear-import/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fusion-plugin-examples/linear-import",
-  "version": "0.1.19-beta.5",
+  "version": "0.1.19-beta.6",
   "type": "module",
   "exports": {
     ".": {

package/dist/plugins/fusion-plugin-omp-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-omp-runtime/package.json

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

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

@@ -8987,7 +8987,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 +9311,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-openclaw-runtime/package.json

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