@runfusion/fusion 0.77.0-beta.7 → 0.77.0-beta.9

package/dist/plugins/fusion-plugin-cli-printing-press/bundled.js

@@ -5877,6 +5877,8 @@ var tasks = projectSchema.table("tasks", {
   executeRequeueLoopCount: integer("execute_requeue_loop_count").default(0),
   executeRequeueLoopSignature: text("execute_requeue_loop_signature"),
   recoveryRetryCount: integer("recovery_retry_count"),
+  sessionContentionHoldCount: integer("session_contention_hold_count").default(0),
+  sessionContentionWaitReason: text("session_contention_wait_reason"),
   taskDoneRetryCount: integer("task_done_retry_count").default(0),
   // FNXC:Lifecycle 2026-07-16-21:40: FN-8141 skip-bypass taint marker (nullable ISO timestamp).
   bulkCompletionRefusalAt: text("bulk_completion_refusal_at"),
@@ -7799,6 +7801,12 @@ var chatSessions = projectSchema.table("chat_sessions", {
   // FNXC:ChatPinned 2026-07-16-12:00: nullable timestamp persists the active
   // Direct-session pin; the ChatStore enforces the per-scope max-three invariant.
   pinnedAt: text("pinned_at"),
+  // FNXC:MemoryFocus 2026-08-13-15:57: per-conversation read-time memory FOCUS/TOPIC
+  // (migration 0059). NULL/empty ('' normalized to NULL) means the conversation
+  // inherits the whole-project scope; otherwise it scopes fn_memory_search +
+  // proactive recall to this topic. It is a read-time filter only — Stash capture
+  // stays write-anywhere across every conversation.
+  memoryFocus: text("memory_focus"),
   cliSessionFile: text("cli_session_file"),
   inFlightGeneration: jsonb("in_flight_generation"),
   cliExecutorAdapterId: text("cli_executor_adapter_id")
@@ -8228,7 +8236,42 @@ var projectTableNames = [
   "chat_rooms",
   "chat_room_members",
   "chat_room_messages",
-  "chat_token_usage"
+  "chat_token_usage",
+  /*
+  FNXC:WorkspaceCoordination 2026-08-23-20:05:
+  FN-9059 (migration 0060) added these two tables to the schema without registering them here, so
+  every registry consumer under-counted them: the PostgreSQL test harness never TRUNCATEd them
+  between tests (a held `repo:<repo>` lease leaked from one case into the next and made the next
+  land report the previous test's successor as the busy holder), and health compaction skipped them.
+  */
+  "workspace_coordination_leases",
+  "workspace_land_intents",
+  /*
+  FNXC:PgTableRegistry 2026-08-23-16:05:
+  Second occurrence of the FN-9059 omission above, found by a leaking `current_plan_evidence` row:
+  a task's plan-evidence version counter continued across tests (a fresh KB-002 started at v2), so
+  `task-dependency-mutation.pg` asserted version 2 and read 3 in a whole-file run while passing in
+  isolation. Every table declared with `projectSchema.table(...)` must be registered here — the
+  harness reset and health compaction both drive off this list, and an unregistered table is simply
+  never cleaned. `project-table-registry.test.ts` now fails when the two drift apart.
+  */
+  "chat_session_tags",
+  "chat_tags",
+  "configuration_revisions",
+  "current_plan_evidence",
+  "mission_lineage_stops",
+  "spec_drift_reports",
+  "spec_locks",
+  "symbol_locks",
+  "task_lifecycle_consumer_cursors",
+  "task_lifecycle_consumer_dead_letters",
+  "task_lifecycle_consumer_receipts",
+  "task_lifecycle_consumer_registrations",
+  "task_lifecycle_event_seq",
+  "task_lifecycle_events",
+  "task_verification_requests",
+  "unplanned_execution_blocks",
+  "workflow_agent_capacity_leases"
 ];
 
 // ../core/src/postgres/schema/central.ts
@@ -9091,6 +9134,7 @@ var DEFAULT_GLOBAL_SETTINGS = {
   defaultProjectId: void 0,
   setupComplete: void 0,
   cliOnboardingCompletedAt: void 0,
+  githubStarPromptDismissedAt: void 0,
   favoriteProviders: void 0,
   favoriteModels: void 0,
   openrouterModelSync: true,
@@ -9120,7 +9164,10 @@ var DEFAULT_GLOBAL_SETTINGS = {
   /* FNXC:UpdateAutomation 2026-08-21-02:48: Keep these schema keys unset because defaults merge into effective settings and `undefined` is distinct from explicit false. */
   autoUpdateEnabled: void 0,
   autoRestartAfterUpdate: void 0,
-  autoReloadOnVersionChange: true,
+  /*
+  FNXC:VersionAutoReload 2026-08-23-04:03:
+  Version-change reload is mandatory, so its key is retired. Older persisted values are ignored because GLOBAL_SETTINGS_KEYS derives from this object and rejects unknown keys before save patches.
+  */
   githubTrackingDefaultRepo: void 0,
   reportRoadmapDedupeEnabled: void 0,
   reportRoadmapLabel: void 0,
@@ -9513,12 +9560,16 @@ var DEFAULT_PROJECT_SETTINGS = {
   executorEscalationProvider: void 0,
   executorEscalationModelId: void 0,
   executorEscalationNodeId: void 0,
-  reviewConvergenceEscalationEnabled: true,
-  reviewConvergenceEscalationProvider: void 0,
-  reviewConvergenceEscalationModelId: void 0,
-  reviewArbitrationEnabled: true,
-  reviewArbitrationProvider: void 0,
-  reviewArbitrationModelId: void 0,
+  /*
+  FNXC:ReviewConvergence 2026-08-23-21:05:
+  FN-149's six review-convergence/arbitration keys are declared in BUILTIN_WORKFLOW_SETTINGS, which
+  the U4 hard-move made the SINGLE source of truth for a moved key's default. Re-declaring them here
+  put them back in the legacy object the hard-move emptied, so an undeclared key on a custom workflow
+  could resolve to this literal instead of the declaration default — the exact drift
+  `workflow-settings-fallback-alignment` guards. The declaration defaults are identical (both
+  `*Enabled` default true, the provider/model lanes carry no default), and the reader uses
+  `!== false`, so removing them here preserves behaviour and restores the invariant.
+  */
   /**
    * FNXC:Merge 2026-06-26-00:00:
    * New and unconfigured projects default AI merge to sync a dirty checked-out integration branch, restoring the legacy stash → fast-forward → restore landing behavior. Explicit persisted merger.allowDirtyLocalCheckoutSync values still win, and no existing-project migration stamps this default into storage.
@@ -9711,6 +9762,40 @@ var DEFAULT_PROJECT_SETTINGS = {
   taskEvaluationRetention: void 0,
   memoryEnabled: true,
   memoryBackendType: "qmd",
+  // FNXC:StashConfig 2026-08-13-16:35: (RUFU-068) Optional per-project Stash LCM
+  // memory backend config. stashUrl points at the operator's Stash server
+  // (default http://127.0.0.1:3457). stashApiKey is an override for hard
+  // isolation (separate Stash instance/account); the PRIMARY API key lives in
+  // the global secrets store ("stash-api-key") and is NEVER committed. Project
+  // value wins over global. TencentDB's URL setting is intentionally NOT ported.
+  stashUrl: "",
+  stashApiKey: "",
+  /*
+  FNXC:Rufu126VectorSearch 2026-08-19-10:50:
+  RUFU-126 (D3): opt-in vector (semantic) recall for the Stash memory backend.
+  Default OFF — zero behavior change until the operator enables it (this is a
+  prototype; rejected alternative was automatic capability detection, which
+  would change default behavior and pay a per-process 404 round-trip against
+  unpatched servers). When true, multi-word (≥2 tokens) recall queries try the
+  Stash GET /api/v1/me/sessions/events/semantic-search endpoint first and fall
+  back byte-identically to the RUFU-121 keyword path on any vector failure
+  (see memory-backend-stash.ts search() + docs/research/stash-vector-search-evaluation.md
+  for D1–D5). Schema-only, consistent with stashUrl/stashApiKey (no UI row).
+  */
+  stashVectorSearch: false,
+  /*
+  FNXC:StashSessionCapture 2026-08-19-04:37:
+  (RUFU-122) Task-terminal transcript upload defaults. All are inert unless
+  memoryBackendType === "stash". executorSessionCaptureEnabled gates ONLY the
+  transcript upload (the RUFU-068 terminal anchor event still fires when it is
+  off) and defaults ON. executorSessionCaptureMaxEvents caps transcript events
+  per task; the engine keeps the most recent N (default 20000).
+  executorSessionCaptureIncludeStatus is the schema-only "keep a setting" for
+  uploading `status` log entries (default off; no UI row).
+  */
+  executorSessionCaptureEnabled: true,
+  executorSessionCaptureMaxEvents: 2e4,
+  executorSessionCaptureIncludeStatus: false,
   memoryAutoSummarizeEnabled: false,
   memoryAutoSummarizeThresholdChars: 5e4,
   memoryAutoSummarizeSchedule: "0 3 * * *",
@@ -10411,6 +10496,20 @@ function classifyWorkflowAgentNode(node) {
   }
 }
 
+// ../core/src/workflows/workflow-merge-region.ts
+var MERGE_REGION_ENTRY_NODE_KINDS = /* @__PURE__ */ new Set([
+  "merge-gate",
+  "merge-attempt",
+  "manual-merge-hold",
+  "retry-backoff",
+  "recovery-router",
+  "branch-group-member-integration",
+  "branch-group-promotion",
+  "pr-create",
+  "pr-respond",
+  "pr-merge"
+]);
+
 // ../core/src/workflows/workflow-extension-types.ts
 function workflowExtensionRegistryId(pluginId, extensionId) {
   return `plugin:${pluginId}:${extensionId}`;
@@ -10939,18 +11038,7 @@ function reachableFrom(start, outgoing) {
   }
   return seen;
 }
-var INTERPRETER_ENTRY_NODE_KINDS = /* @__PURE__ */ new Set([
-  "merge-gate",
-  "merge-attempt",
-  "manual-merge-hold",
-  "retry-backoff",
-  "recovery-router",
-  "branch-group-member-integration",
-  "branch-group-promotion",
-  "pr-create",
-  "pr-respond",
-  "pr-merge"
-]);
+var INTERPRETER_ENTRY_NODE_KINDS = MERGE_REGION_ENTRY_NODE_KINDS;
 var MERGE_CLASS_NODE_KINDS = /* @__PURE__ */ new Set([
   "merge-gate",
   "merge-attempt",
@@ -12970,6 +13058,13 @@ Lint, tests, and typecheck are also hard quality gates:
 - Keep fixing failures caused by your change until lint, impacted tests, build, and typecheck pass.
 - If the repository exposes a typecheck command, run it and fix failures caused by your change.
 - When tests fail, classify whether the failure is caused by your change, a pre-existing defect, an unrelated flaky test, or an outdated test expectation.
+
+**A behavior change owns every test that asserts the old behavior.** Targeted verification runs the tests for files you TOUCHED; the tests encoding the behavior you just changed usually live in files you did NOT touch, so a green targeted run is not evidence that none exist. Before finishing, search for them:
+- Added a guard, validation, or required field? Grep for the FIXTURES it will now refuse \u2014 they are outside your File Scope \u2014 and fix each to state its intent explicitly.
+- Removed a feature? Delete its tests. A test asserting a deliberately removed contract guards nothing, and making it pass later means re-adding removed behavior.
+- Changed an order, default, constant, or prompt string? Grep for the literal; topology lists, prompt-content assertions, and size budgets live far from the code they describe.
+- Added a public store/service method? Update the inventory/drift guards that require every public surface to be classified.
+Fix at the SHARED FIXTURE FACTORY, not per test \u2014 one helper usually explains dozens of failures. Never make a stale test pass by weakening it: update the fixture, record the new truth, or delete the test naming the change that removed its subject.
 - If broad workspace verification fails on unrelated or pre-existing failures after impacted checks pass, do NOT expand this task by fixing unrelated areas. Log the evidence, quarantine flakes per project policy, or create/link a follow-up task.
 - Do not repeatedly rerun a broad failing or hanging workspace command without a new hypothesis and a narrower confirming command.
 
@@ -13242,6 +13337,7 @@ files with assertions that run via a test runner. Typechecks and builds are NOT
 tests. Manual verification is NOT a test.
 
 - Each implementation step should include writing tests for the code being changed
+- **If the task CHANGES, GATES, or REMOVES existing behavior, include a step to find and update the tests that assert the OLD behavior.** Name the search in that step: the fixtures a new guard will now refuse, the tests of a removed feature, or the literal to grep for a changed order/default/constant/prompt string. Those tests live OUTSIDE the File Scope, so targeted verification will not surface them and the executor will not find them by accident. Measured 2026-08-24: five such changes left ~135 stale failing tests behind, every one having passed its own targeted verification; one shared fixture line accounted for 37 of them.
 - For bug fixes and UI-affordance add/remove tasks, the spec MUST include a \`## Surface Enumeration\` section. The workflow Plan Review gate validates this before execution when plan review is enabled; missing coverage is a blocking REVISE.
 - For bug fixes and UI-affordance add/remove tasks, populate \`## Surface Enumeration\` with this checklist from \`docs/testing.md\`: providers/bridges/execution paths; desktop + mobile breakpoints/platforms; empty/undefined/duplicate/populated data states; shared hooks/components/modules/helpers; every component that renders the affordance; leftover shells after removal.
 - For bug fixes and UI-affordance add/remove tasks, regression tests must assert the invariant across all known surfaces \u2014 enumerate every provider/bridge, desktop + mobile breakpoints, empty/undefined/populated data states, and for UI-affordance changes every component rendering the affordance plus leftover shells after removal \u2014 not just the reported repro (see FN-5787/FN-5789/FN-5803, FN-5751, and FN-6115/FN-6118/FN-6123)
@@ -14037,10 +14133,59 @@ var DEFAULT_TRIAGE_PROMPT = BUILTIN_AGENT_PROMPTS.find((prompt) => prompt.id ===
 var DEFAULT_TRIAGE_FAST_PROMPT = BUILTIN_AGENT_PROMPTS.find((prompt) => prompt.id === "default-triage-fast")?.prompt ?? "";
 var DEFAULT_REVIEWER_PROMPT = BUILTIN_AGENT_PROMPTS.find((prompt) => prompt.role === "reviewer")?.prompt ?? "";
 var DEFAULT_MERGER_PROMPT = BUILTIN_AGENT_PROMPTS.find((prompt) => prompt.role === "merger")?.prompt ?? "";
+var REVIEW_GATE_STEP_TEMPLATE_START = "### Step {N-1}: Testing & Verification";
+var REVIEW_GATE_STEP_TEMPLATE_END = "## Documentation Requirements";
+var REVIEW_GATED_STEP_CONTRACT = `## Review-gated step contract (OVERRIDES the step template above)
+
+This workflow runs testing, verification, documentation, and delivery as REVIEW-COLUMN GATES after
+implementation. They are not task steps here.
+
+- Do NOT emit a "Testing & Verification" step.
+- Do NOT emit a "Documentation & Delivery" step.
+- Emit implementation steps only, ending with the last implementation step.
+- Per-step verification bullets stay: each implementation step still runs its own targeted tests.
+
+`;
+function applyReviewGatedStepContract(prompt) {
+  const start = prompt.indexOf(REVIEW_GATE_STEP_TEMPLATE_START);
+  const end = prompt.indexOf(REVIEW_GATE_STEP_TEMPLATE_END);
+  if (start < 0 || end < 0 || end <= start) {
+    return `${prompt}
+
+${REVIEW_GATED_STEP_CONTRACT}`;
+  }
+  return `${prompt.slice(0, start)}${REVIEW_GATED_STEP_CONTRACT}${prompt.slice(end)}`;
+}
+var DOCUMENTATION_STEP_TEMPLATE_START = "### Step {N}: Documentation & Delivery";
+var DOCUMENTATION_STEP_TEMPLATE_END = "## Documentation Requirements";
+var NO_DOCUMENTATION_STEP_CONTRACT = `## Documentation is not a step (OVERRIDES the step template above)
+
+Do NOT emit a "Documentation & Delivery" step. "Testing & Verification" is the LAST step.
+
+- **Repository documentation is implementation work.** When a change makes an existing doc wrong,
+  update that doc inside the step that made the change, so it is reviewed together with the code.
+  Never plan it as its own step, and never gate completion on it when the change documents nothing.
+- **Fusion-side delivery is not yours to plan.** The card summary, the delivery note, artifact
+  registration, and out-of-scope follow-up tasks are produced by a review-column milestone after the
+  review passes. Do not emit steps or checklist items for any of them.
+
+`;
+function stripDocumentationDeliveryStep(prompt) {
+  const start = prompt.indexOf(DOCUMENTATION_STEP_TEMPLATE_START);
+  const end = prompt.indexOf(DOCUMENTATION_STEP_TEMPLATE_END);
+  if (start < 0 || end < 0 || end <= start) {
+    return `${prompt}
+
+${NO_DOCUMENTATION_STEP_CONTRACT}`;
+  }
+  return `${prompt.slice(0, start)}${NO_DOCUMENTATION_STEP_CONTRACT}${prompt.slice(end)}`;
+}
 var BUILTIN_SEAM_PROMPTS = {
   execute: DEFAULT_EXECUTOR_PROMPT,
   planning: DEFAULT_TRIAGE_PROMPT,
   "planning-fast": DEFAULT_TRIAGE_FAST_PROMPT,
+  /* Review-gated tasks keep test and delivery work in review-column gates. */
+  "planning-implementation-only": applyReviewGatedStepContract(DEFAULT_TRIAGE_PROMPT),
   "step-execute": DEFAULT_EXECUTOR_PROMPT,
   review: DEFAULT_REVIEWER_PROMPT,
   merge: DEFAULT_MERGER_PROMPT
@@ -14308,6 +14453,7 @@ function postMergeVerificationOptionalGroupNode(column = "done") {
 }
 
 // ../core/src/workflows/builtin-plan-review-group.ts
+var IMPLEMENTATION_ONLY_STEPS_CRITERION = "\n\n## Review-gated implementation steps\nREVISE when the proposed task-step list includes testing, verification, documentation, or delivery work. Those are review-column gates in this workflow, not implementation steps.";
 var PLAN_REVIEW_GROUP_ID = "plan-review";
 var PLAN_REVIEW_STEP_NODE_ID = "plan-review-step";
 var PLAN_REVIEW_NAME = "Plan Review";
@@ -14349,6 +14495,10 @@ function planReviewOptionalGroupNode(column, options = {}) {
     toolMode: "readonly",
     gateMode: "gate"
   };
+  if (options.requireImplementationOnlySteps === true) {
+    promptConfig.prompt = `${PLAN_REVIEW_PROMPT}${IMPLEMENTATION_ONLY_STEPS_CRITERION}`;
+    promptConfig.requireImplementationOnlySteps = true;
+  }
   if (options.requireExternalIntegrationEvidence === true) {
     promptConfig.requireExternalIntegrationEvidence = true;
   }
@@ -14389,6 +14539,7 @@ function planReviewOptionalGroupNode(column, options = {}) {
 var PLAN_REPLAN_NODE_ID = "plan-replan";
 var BROWSER_VERIFICATION_REMEDIATION_NODE_ID = "browser-verification-remediation";
 var CODE_REVIEW_REMEDIATION_NODE_ID = "code-review-remediation";
+var REVIEW_GATED_CODE_REVIEW_REMEDIATION_NODE_ID = "code-review-remediation-steps";
 function planReplanNode(column = "triage") {
   return {
     id: PLAN_REPLAN_NODE_ID,
@@ -14415,6 +14566,14 @@ function browserVerificationRemediationNode(column = "in-progress") {
     }
   };
 }
+function codeReviewRemediationStepsNode(column = "in-progress") {
+  return {
+    id: REVIEW_GATED_CODE_REVIEW_REMEDIATION_NODE_ID,
+    kind: "prompt",
+    column,
+    config: { name: "Code review remediation", workflowAction: "review-remediation-steps", forWorkflowStepId: "code-review", toolMode: "readonly" }
+  };
+}
 function codeReviewRemediationNode(column = "in-progress") {
   return {
     id: CODE_REVIEW_REMEDIATION_NODE_ID,
@@ -15063,6 +15222,147 @@ var RAW_BUILTIN_CODING_IDEAS_WORKFLOW_IR = (() => {
 })();
 var BUILTIN_CODING_IDEAS_WORKFLOW_IR = parseWorkflowIr(RAW_BUILTIN_CODING_IDEAS_WORKFLOW_IR);
 
+// ../core/src/workflows/builtin-documentation-delivery-group.ts
+var DOCUMENTATION_DELIVERY_GROUP_ID = "documentation-delivery";
+var DOCUMENTATION_DELIVERY_PROMPT = `Report on the accepted implementation exactly once, for the operator who reads this card later.
+
+You have NO writer. This session can read, search and list \u2014 nothing else. Everything durable you
+produce is the text you output here. Do not call a tool to save it, do not claim you saved anything,
+and do not modify repository files: the code has already been reviewed and must not change now.
+
+## 1. The card summary (always)
+
+Open with 2-4 sentences of plain prose an operator can read to know what shipped and why. Mention
+user-visible behaviour or important files when they matter, and how it was verified. No headings, no
+bullet lists, no process narration, no verdict. This text becomes the task's summary.
+
+## 2. Follow-up proposals (only when they genuinely exist)
+
+If the work surfaced worthwhile follow-up ideas OUTSIDE this task's scope, end your output with one
+fenced JSON block, and nothing after it:
+
+\`\`\`json
+{"recommendations":[{"id":"stable-slug","title":"short title","description":"what to do and why","category":"improvement"}]}
+\`\`\`
+
+- \`category\` is one of: improvement, feature, bug, other.
+- Each \`id\` must be unique and stable.
+- These are PROPOSALS for a human, not work orders and not tasks: an operator decides which become
+  tasks. You cannot create tasks and must not try.
+- Ground every entry in something you actually saw. Omit the block entirely rather than invent work,
+  restate this task, or pad the list. Fewer, real proposals are the correct answer.
+- Never put commands, shell syntax, credentials or secrets in a proposal.
+
+You cannot block this card and you have no verdict to give. If something is missing or you could not
+determine it, say so plainly in the summary and finish.`;
+function documentationDeliveryOptionalGroupNode(column) {
+  return {
+    id: DOCUMENTATION_DELIVERY_GROUP_ID,
+    kind: "optional-group",
+    column,
+    config: {
+      name: "Documentation",
+      defaultOn: true,
+      /*
+      FNXC:ReportingOnlyGroup 2026-08-26-06:56:
+      Documentation ONLY documents. `gateMode: "advisory"` on the inner node was not enough and the
+      gap was measured on a real card: its REVISE recorded `advisory_failure`, which held the merge
+      door ("no current approval") AND bounced the card to implementation with no work to do, where
+      it re-ran Code Review against an unchanged tree and merged on the second pass by luck.
+      `reportingOnly` states the contract once: no approval to withhold, no remediation to request.
+      */
+      reportingOnly: true,
+      template: {
+        nodes: [{
+          id: "documentation-delivery-step",
+          kind: "prompt",
+          config: {
+            name: "Documentation",
+            prompt: DOCUMENTATION_DELIVERY_PROMPT,
+            toolMode: "readonly",
+            gateMode: "advisory",
+            workflowAction: "documentation-delivery",
+            /* The two projection contracts that give a writer-less node durable output. */
+            summaryTarget: "task",
+            recommendationsTarget: "task"
+          }
+        }],
+        edges: []
+      }
+    }
+  };
+}
+
+// ../core/src/workflows/builtin-coding-ideas-v2-workflow-ir.ts
+var clone = (ir) => JSON.parse(JSON.stringify(ir));
+var RAW_BUILTIN_CODING_IDEAS_V2_WORKFLOW_IR = (() => {
+  const ir = clone(BUILTIN_CODING_IDEAS_WORKFLOW_IR);
+  ir.name = "builtin-coding-ideas-v2";
+  const plan = ir.nodes.find((node) => node.id === "plan");
+  if (!plan?.config) throw new Error("coding-ideas-v2 requires the inherited planning node");
+  plan.config.prompt = stripDocumentationDeliveryStep(String(plan.config.prompt ?? ""));
+  const parse = ir.nodes.find((node) => node.id === "parse");
+  if (parse) parse.config = { ...parse.config, implementationOnlySteps: true, preserveRemediationSteps: true };
+  const codeReviewRemediation = ir.nodes.find((node) => node.id === "code-review-remediation");
+  if (codeReviewRemediation) {
+    codeReviewRemediation.config = {
+      ...codeReviewRemediation.config,
+      ...codeReviewRemediationStepsNode().config,
+      name: "Code Review Remediation"
+    };
+  }
+  const codeReviewIndex = ir.nodes.findIndex((node) => node.id === "code-review");
+  if (codeReviewIndex < 0) throw new Error("coding-ideas-v2 requires the inherited code-review gate");
+  const codeReviewStep = ir.nodes[codeReviewIndex]?.config?.template?.nodes?.find((node) => node.id === "code-review-step");
+  if (!codeReviewStep?.config) throw new Error("coding-ideas-v2 requires the inherited code-review-step template node");
+  codeReviewStep.config.prompt = `${String(codeReviewStep.config.prompt ?? "")}
+
+## Step 0: Judge the TESTS before you judge the code
+
+You cannot run anything: this session is read-only, \`bash\` is denied and no verification tool is
+available to you. Do not claim you ran lint, tests or a build, and do not ask for a command to be
+run. The executor already wrote and ran the tests; your job is to rule on whether that work is
+sound.
+
+Read the test files in the diff and rule on FOUR things:
+
+1. **They exist.** A behavioural change with no test is a REVISE. Say which change is uncovered.
+2. **They are real tests.** Assertions executed by a test runner. A typecheck is not a test, a build
+   is not a test, and manual verification is not a test.
+3. **They assert BEHAVIOUR.** Never a comment, a date stamp, or prose lifted from source. Asserting
+   that a comment exists tests nothing a user or caller can observe. Code-construct guards
+   (call-site allowlists, architectural ratchets) are legitimate and stay.
+4. **They cover the INVARIANT, not just the reported case.** For a bug fix, a test that only
+   reproduces the single reported symptom is incomplete: require every known surface. If this task
+   CHANGED, GATED or REMOVED behaviour, the tests that encoded the OLD behaviour must have been
+   updated or deleted in the same change \u2014 they live outside the File Scope and targeted
+   verification will not have surfaced them.
+
+Then review the code itself for what tests do not catch: logic errors, broken edge cases, and
+unhandled failure modes.`;
+  ir.nodes.splice(codeReviewIndex + 1, 0, documentationDeliveryOptionalGroupNode("in-review"));
+  const summaryIndex = ir.nodes.findIndex((node) => node.id === "completion-summary");
+  if (summaryIndex >= 0) ir.nodes.splice(summaryIndex, 1);
+  ir.edges = ir.edges.filter((edge) => edge.from !== "completion-summary" && edge.to !== "completion-summary");
+  ir.edges = ir.edges.filter((edge) => !(edge.from === "code-review" && edge.to === "merge-gate"));
+  ir.edges.push(
+    { from: "steps", to: "code-review", condition: "success" },
+    { from: "code-review", to: "documentation-delivery", condition: "success" },
+    { from: "documentation-delivery", to: "merge-gate", condition: "success" },
+    /*
+    FNXC:CodingIdeasV2Workflow 2026-08-25-10:20:
+    Documentation is ADVISORY: it reports, it never vetoes. Its failure edge reaches the merge gate
+    exactly like its success edge, so a delivery note that could not be written cannot strand a
+    card whose code is already approved. Measured why: as a blocking gate it bounced a task whose
+    own plan said not to implement anything ("No task-specific implementation is present"), and the
+    card looped through the review lane every five minutes indefinitely.
+    */
+    { from: "documentation-delivery", to: "merge-gate", condition: "failure" }
+  );
+  return ir;
+})();
+var BUILTIN_CODING_IDEAS_V2_WORKFLOW_IR = parseWorkflowIr(RAW_BUILTIN_CODING_IDEAS_V2_WORKFLOW_IR);
+
 // ../core/src/workflows/builtin-brainstorming-workflow-ir.ts
 var APPROVAL_PHRASE = "looks good";
 var RAW_BUILTIN_BRAINSTORMING_WORKFLOW_IR = (() => {
@@ -15818,6 +16118,47 @@ var BUILTIN_WORKFLOWS = [
     createdAt: BUILTIN_TS,
     updatedAt: BUILTIN_TS
   },
+  /*
+   * FNXC:CodingIdeasV2Workflow 2026-08-26-05:56:
+   * Same Ideas board as builtin:coding-ideas, with one rule: in-review NEVER writes code.
+   * Implementation and its tests finish in `in-progress` — the executor's own final verification
+   * runs the project's configured test/build commands there, and a red result appends named fix
+   * steps rather than letting the card advance. `in-review` is then three read-only milestones:
+   * Code Review judges, Documentation reports, and the merge is the last thing that happens.
+   * The layout is ordered left-to-right in that same sequence so the editor's diagram reads the way
+   * the graph runs; nodes deleted from the graph must be deleted from this map too, or the editor
+   * keeps positioning ghosts.
+   */
+  {
+    id: "builtin:coding-ideas-v2",
+    name: "Coding (Ideas) V2",
+    description: "Capture-first coding pipeline with a read-only review lane: park ideas in a manual intake, plan, implement and test per step, then review, document, and merge.",
+    kind: "workflow",
+    ir: BUILTIN_CODING_IDEAS_V2_WORKFLOW_IR,
+    layout: {
+      start: { x: 60, y: 160 },
+      plan: { x: 230, y: 160 },
+      "plan-review": { x: 400, y: 160 },
+      "plan-replan": { x: 400, y: 320 },
+      "plan-review-no-op": { x: 570, y: 320 },
+      parse: { x: 570, y: 160 },
+      steps: { x: 740, y: 160 },
+      "review-pending-handoff": { x: 740, y: 320 },
+      "code-review": { x: 910, y: 160 },
+      "code-review-remediation": { x: 910, y: 320 },
+      "documentation-delivery": { x: 1080, y: 160 },
+      "merge-gate": { x: 1250, y: 160 },
+      "branch-group-member-integration": { x: 1420, y: 80 },
+      "branch-group-promotion": { x: 1590, y: 80 },
+      "merge-manual-hold": { x: 1420, y: 240 },
+      "merge-attempt": { x: 1760, y: 160 },
+      "merge-retry": { x: 1930, y: 80 },
+      "recovery-router": { x: 1930, y: 240 },
+      end: { x: 2100, y: 160 }
+    },
+    createdAt: BUILTIN_TS,
+    updatedAt: BUILTIN_TS
+  },
   {
     id: "builtin:legacy-coding",
     name: "Legacy coding",

package/dist/plugins/fusion-plugin-cli-printing-press/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fusion-plugin-examples/cli-printing-press",
-  "version": "0.1.53-beta.7",
+  "version": "0.1.53-beta.9",
   "type": "module",
   "exports": {
     ".": {