@productbrain/mcp 0.0.1-beta.53 → 0.0.1-beta.55

package/dist/{chunk-QUWYOGHB.js → chunk-HQLEMADT.js}

@@ -38,7 +38,7 @@ import {
   unknownAction,
   validationResult,
   withEnvelope
-} from "./chunk-WEH5CZJ7.js";
+} from "./chunk-U4ABXFUT.js";
 import {
   trackQualityCheck,
   trackQualityVerdict
@@ -232,7 +232,7 @@ ${formatted}` }],
     },
     withEnvelope(async ({ entryId }) => {
       requireWriteAccess();
-      const { runContradictionCheck } = await import("./smart-capture-3OXWEXWM.js");
+      const { runContradictionCheck } = await import("./smart-capture-6IM4EMLF.js");
       const entry = await mcpQuery("chain.getEntry", { entryId });
       if (!entry) {
         return notFoundResult(entryId, `Entry '${entryId}' not found. Try search to find the right ID.`);
@@ -2639,9 +2639,9 @@ function validateWorkflowDescriptor(descriptor) {
       `Workflow '${descriptor.id}' is facilitated and must define runtime.primaryTool.`
     );
   }
-  if (descriptor.output.summaryCapture?.createsPrimaryRecord && descriptor.output.primaryRecord.routing.mode !== "fixed") {
+  if (descriptor.output.summaryCapture?.createsPrimaryRecord && descriptor.output.primaryRecord.routing.mode === "fixed" && descriptor.output.summaryCapture.descriptionField === "") {
     throw new Error(
-      `Workflow '${descriptor.id}' cannot define summaryCapture when primaryRecord routing is classifier-based.`
+      `Workflow '${descriptor.id}' summaryCapture.descriptionField cannot be empty.`
     );
   }
 }
@@ -2651,13 +2651,10 @@ function getWorkflowSummaryCaptureDefinition(descriptor) {
   if (!summaryCapture || !summaryCapture.createsPrimaryRecord) {
     return null;
   }
-  if (routing.mode !== "fixed") {
-    return null;
-  }
   return {
-    collection: routing.collection,
+    routing: routing.mode === "fixed" ? { mode: "fixed", collection: routing.collection } : { mode: "classifier" },
     nameTemplate: summaryCapture.nameTemplate,
-    descriptionField: summaryCapture.descriptionField ?? "description",
+    descriptionField: summaryCapture.descriptionField,
     descriptionSource: summaryCapture.descriptionSource ?? "final-output-text"
   };
 }
@@ -2696,9 +2693,9 @@ function compileWorkflowDefinition(descriptor) {
     facilitatorPreamble: clonedDescriptor.facilitatorPreamble,
     rounds: clonedDescriptor.rounds,
     kbOutputCollection: primaryRecordCollection ?? void 0,
-    kbOutputTemplate: summaryCapture ? {
+    kbOutputTemplate: summaryCapture && summaryCapture.routing.mode === "fixed" ? {
       nameTemplate: summaryCapture.nameTemplate,
-      descriptionField: summaryCapture.descriptionField
+      descriptionField: summaryCapture.descriptionField ?? "description"
     } : void 0,
     errorRecovery: clonedDescriptor.errorRecovery
   };
@@ -2724,7 +2721,7 @@ var RETRO_WORKFLOW_DESCRIPTOR = {
 4. **Create a Plan** at the start showing all rounds as tasks. Update it as you progress.
 5. **Synthesize between rounds.** After collecting input, reflect back what you heard before moving on.
 6. **Never go silent.** If something fails, say what happened and what to do next.
-7. **Commit to the Chain** at the end using the Product OS capture tool.
+7. **Finalize through the workflow substrate.** Complete the terminal round with \`workflows action=checkpoint ... isFinal=true\` so the durable run creates the retro draft record.
 8. **Match the energy.** Be warm but structured. This is a ceremony, not a checklist.
 
 ## Communication Style
@@ -2848,7 +2845,7 @@ Create a Cursor Plan with these rounds as tasks. Mark each in_progress as you en
       label: "Close & Capture",
       type: "close",
       instruction: "One last thing \u2014 in one sentence, what's the single most important thing you're taking away from this retro?",
-      facilitatorGuidance: "Keep it brief. One sentence reflection. Then summarize the entire retro: scope, key wins, key pain points, patterns identified, actions committed. Ask if they want to commit this to the Chain. If yes, use capture to create a decision/tension entry. Thank them for the retro.",
+      facilitatorGuidance: "Keep it brief. One sentence reflection. Then summarize the entire retro: scope, key wins, key pain points, patterns identified, actions committed. Finalize the durable run through `workflows action=checkpoint` with `isFinal=true` so the retro draft record is created via the workflow substrate. Then ask if they want to commit that draft to the Chain. Thank them for the retro.",
       outputSchema: {
         field: "takeaway",
         description: "Single-sentence takeaway",
@@ -2876,7 +2873,7 @@ Create a Cursor Plan with these rounds as tasks. Mark each in_progress as you en
   },
   errorRecovery: `If anything goes wrong during the retro:
 
-1. **MCP tool failure**: Skip the chain commit step. Summarize everything in the conversation instead. Suggest the participant runs \`capture\` manually later.
+1. **MCP tool failure**: Skip the workflow finalization step. Summarize everything in the conversation instead. Suggest retrying \`workflows action=checkpoint\` later or capturing manually if needed.
 2. **AskQuestion not available**: Fall back to numbered options in plain text. "Reply with 1, 2, or 3."
 3. **Plan creation fails**: Continue without the Plan. The conversation IS the record.
 4. **Participant goes off-topic**: Gently redirect: "That's valuable \u2014 let's capture it. For now, let's stay with [current round]."
@@ -3124,10 +3121,18 @@ var IMPLEMENTATION_REVIEW_WORKFLOW_DESCRIPTOR = {
   icon: "\u2713",
   facilitatorPreamble: `You are now in **Implementation Review Mode**. You orchestrate a structured review of work that was just built \u2014 not a conversation, but a tool-driven audit with sub-agent support.
 
+## Review scope (CRITICAL)
+
+- **Default scope is this conversation only.** Only the work discussed or produced in this conversation is in scope. Do not review or touch files, BETs, or work outside that scope unless the user explicitly expands it (e.g. "also review the auth module").
+- **Infer scope first.** Use conversation context, git status/diff, and recent edits to determine which BET, feature, or files are in scope. Call orient/start and \`context action=gather\` with the inferred scope; do not ask the user to pick what to review unless it's ambiguous.
+- **Ask only to clarify boundaries.** If scope is ambiguous after inference, ask a single, focused question to clarify (e.g. "Should this review include only the changes we just made, or the whole feature?"). Do not ask open-ended "what should we review?" or "which work area?" unless inference failed.
+- **State scope explicitly in Round 01.** After orient and context gather, state in one sentence what is in scope (e.g. "Scope: changes in this conversation for BET-72" or "Scope: files X, Y and BET-72"). Confirm only if the user might reasonably expect something else.
+- **Sub-agents and tools are scope-bound.** When spawning sub-agents or calling verify/review-against-rules, restrict attention to the scoped work only. Do not audit or suggest changes to code outside the stated scope.
+
 ## Your Behavior
 
 1. **Tool-heavy, not chat-heavy.** Each round calls specific tools: orient, quality, verify, chain-review, context action=gather, review-against-rules. Use Context7 (query-docs) for relevant testing and framework docs \u2014 not for Chain truth.
-2. **Spawn sub-agents** for parallel review: (a) code/architecture review, (b) test honesty (did we edit tests to pass or do they validate real behavior?), (c) Chain/standards coherence. Max 2 agents in parallel, 30s budget each.
+2. **Spawn sub-agents** for parallel review: (a) code/architecture review, (b) test honesty (did we edit tests to pass or do they validate real behavior?), (c) Chain/standards coherence. Max 2 agents in parallel, 30s budget each. **Constrain each sub-agent to the stated review scope only.**
 3. **Chain is SSOT.** Call orient or start first. Use entries action=search and context action=gather to load relevant BETs, DECs, BRs. If findings conflict with Chain entries, report the conflict and cite the entry ID.
 4. **One round at a time.** Complete each round before moving to the next. Checkpoint progress.
 5. **CRITICAL: End with BET/chain IDs.** The final output MUST include a single sentence: "BET/feature IDs reviewed: [IDs]. [One-line summary of findings]."
@@ -3153,11 +3158,11 @@ When reviewing test results: (a) test staleness \u2014 code changed, test not up
       num: "01",
       label: "Orient & Scope",
       type: "open",
-      instruction: "Load governance and scope. What BET or work are we reviewing? Call orient or start. Use context action=gather with the BET/feature ID.",
-      facilitatorGuidance: "Call orient or start to load workspace governance and active bets. Ask the participant which BET, feature, or work area to review. Use context action=gather task='implementation review for [BET-ID]' to load related entries. Present: scope, relevant BETs/DECs/BRs, and any stale entries orient surfaces.",
+      instruction: "Apply the Review scope rules: infer scope from this conversation, git diff, and recent edits (default = work in this conversation only). Call orient or start, then context action=gather for the inferred BET/feature. State scope in one explicit sentence. Only ask the participant if scope is ambiguous.",
+      facilitatorGuidance: "Infer scope from conversation context, git status/diff, and recent edits \u2014 default is work in this conversation only. Call orient or start to load governance and active bets. Use context action=gather task='implementation review for [inferred-BET-or-feature]' to load related entries. State scope explicitly in one sentence (e.g. 'Scope: changes in this conversation for BET-72'). Present: stated scope, relevant BETs/DECs/BRs, and any stale entries orient surfaces. Ask the participant only if scope is ambiguous (e.g. 'Only the files we changed, or the whole feature?').",
       outputSchema: {
         field: "scope",
-        description: "BET/feature IDs and related Chain context",
+        description: "Explicit scope statement plus BET/feature IDs and related Chain context",
         format: "structured"
       },
       maxDurationHint: "3 min"
@@ -3181,8 +3186,8 @@ When reviewing test results: (a) test staleness \u2014 code changed, test not up
       num: "03",
       label: "Code & Test Honesty",
       type: "open",
-      instruction: "Spawn sub-agents to review implementation and tests. Did we meet high standards? Are tests validating real behavior or did we edit them just to pass?",
-      facilitatorGuidance: "Spawn 1\u20132 sub-agents in parallel: (1) explore agent \u2014 code review, architecture boundaries, type-safety. (2) generalPurpose agent \u2014 test review: are tests asserting real behavior or were they edited to pass? Use Context7 (query-docs) for relevant testing and framework best practices if needed. Classify any test failures: staleness, regression, or flaky. Synthesize: implementation grade, test honesty verdict, refactoring suggestions.",
+      instruction: "Spawn sub-agents to review implementation and tests for the stated scope only. Did we meet high standards? Are tests validating real behavior or did we edit them just to pass?",
+      facilitatorGuidance: "Restrict all review to the scope stated in Round 01 (by default, work in this conversation only). Spawn 1\u20132 sub-agents in parallel: (1) explore agent \u2014 code review, architecture boundaries, type-safety for scoped files only. (2) generalPurpose agent \u2014 test review for scoped code: are tests asserting real behavior or were they edited to pass? Pass the scope (files/BET) explicitly to sub-agents so they do not touch other work. Use Context7 (query-docs) for relevant testing and framework best practices if needed. Classify any test failures: staleness, regression, or flaky. Synthesize: implementation grade, test honesty verdict, refactoring suggestions (within scope only).",
       outputSchema: {
         field: "codeAndTests",
         description: "Implementation grade, test honesty, refactor suggestions",
@@ -3223,8 +3228,8 @@ When reviewing test results: (a) test staleness \u2014 code changed, test not up
       num: "06",
       label: "Capture & Close",
       type: "close",
-      instruction: "Capture the review as an insight. Use session-wrapup. Thank the participant.",
-      facilitatorGuidance: "Summarize the review for capture. Use capture with collection=insights. Include: BET/feature IDs, verdict, key findings. Run session-wrapup before closing. Thank the participant. Remind them to commit-entry when ready.",
+      instruction: "Finalize the review as an insight draft. Use session-wrapup. Thank the participant.",
+      facilitatorGuidance: "Summarize the review for finalization. Complete the terminal round through `workflows action=checkpoint` with `isFinal=true` so the workflow substrate creates the draft insight record. Include: BET/feature IDs, verdict, key findings. Run session-wrapup before closing. Thank the participant. Remind them to commit-entry when ready.",
       outputSchema: {
         field: "capture",
         description: "Insight entry created, BET IDs referenced",
@@ -3276,15 +3281,15 @@ var PROCESS_CHANGE_WORKFLOW_DESCRIPTOR = {
 2. **Orient first.** Call orient to load workspace context \u2014 but present only what's relevant to the change, not the full briefing.
 3. **Capture the why.** The single most important thing: why is this change happening? The what is usually obvious from the code. The why is what evaporates.
 4. **Link to what exists.** Search the Chain for related entries. If this change was triggered by a tension, bet, or decision \u2014 link it. If it creates a new decision or surfaces a new tension \u2014 capture that too.
-5. **Route via classifier.** Use capture without specifying a collection. The classifier knows where it belongs: tensions for bugs, decisions for choices made, features for new capabilities, insights for lessons learned.
-6. **Don't over-process.** If the user gives you everything in one message, skip to capture. Not every round needs a conversation.
+5. **Finalize through the workflow substrate.** Complete the terminal round with \`workflows action=checkpoint ... isFinal=true\`. The substrate will classifier-route the primary record and attach it to the durable run.
+6. **Don't over-process.** If the user gives you everything in one message, move quickly through the required checkpoints in order, then finalize. Not every round needs a conversation.
 7. **End with the link.** Always finish by connecting the new entry to related Chain knowledge via graph suggest.
 
 ## Tool Usage
 
 - \`orient\` \u2014 load workspace context (governance, active bets, stale entries)
 - \`entries action=search\` \u2014 find related entries
-- \`capture\` \u2014 create the entry (let classifier route)
+- \`capture\` \u2014 manual fallback only if workflow finalization cannot safely route the entry
 - \`graph action=suggest\` \u2014 discover connections
 - \`relations action=create\` or \`relations action=batch-create\` \u2014 link to related entries
 - \`commit-entry\` \u2014 promote to SSOT (only on user confirmation)
@@ -3293,8 +3298,8 @@ var PROCESS_CHANGE_WORKFLOW_DESCRIPTOR = {
 ## Communication Style
 
 - **Conversational, not ceremonial.** No round headers needed unless the user wants structure.
-- **One question at a time.** Ask what you need, capture, move on.
-- **If the user gives rich context upfront**, skip straight to capture and linking. Don't ask questions they already answered.
+- **One question at a time.** Ask what you need, checkpoint, move on.
+- **If the user gives rich context upfront**, checkpoint the answered rounds in order, then finalize and link. Don't ask questions they already answered.
 - **Show what you captured.** Always confirm what went to the Chain before closing.`,
   rounds: [
     {
@@ -3345,7 +3350,7 @@ var PROCESS_CHANGE_WORKFLOW_DESCRIPTOR = {
       label: "Capture & Close",
       type: "close",
       instruction: "Capture to the Chain. Link to related entries. Confirm with the user.",
-      facilitatorGuidance: "Use capture with name and description \u2014 omit collection to let the classifier route. After capture, call graph action=suggest to find connections. Create the top 2-3 relevant relations. Show the user what was captured: entry ID, collection it landed in, relations created. Ask if they want to commit now or leave as draft. If they confirm, commit-entry. If there are stale entries to reconfirm, mention them. Thank the user briefly and exit \u2014 don't linger.",
+      facilitatorGuidance: "Finalize through workflows action=checkpoint with isFinal=true, passing a summaryName when you have a clean title. The workflow substrate will create the primary record as a draft and attach it to the durable run. After finalization, call graph action=suggest to find connections. Create the top 2-3 relevant relations. Show the user what was captured: entry ID, collection it landed in, relations created. Ask if they want to commit now or leave as draft. If they confirm, commit-entry. If there are stale entries to reconfirm, mention them. Thank the user briefly and exit \u2014 don't linger.",
       outputSchema: {
         field: "capture",
         description: "Entry captured, relations created, commit status",
@@ -3359,6 +3364,10 @@ var PROCESS_CHANGE_WORKFLOW_DESCRIPTOR = {
       routing: {
         mode: "classifier"
       }
+    },
+    summaryCapture: {
+      createsPrimaryRecord: true,
+      nameTemplate: "{whatAndWhy}"
     }
   },
   runtime: {
@@ -3710,9 +3719,13 @@ This checkpoint was NOT saved. The conversation context is preserved \u2014 cont
     const descriptor = getWorkflowDescriptor(workflowId);
     const template = descriptor ? getWorkflowTemplateMetadata(descriptor) : { slug: wf.id, name: wf.name };
     const summaryCapture = descriptor ? getWorkflowSummaryCaptureDefinition(descriptor) : wf.kbOutputCollection && wf.kbOutputTemplate ? {
-      collection: wf.kbOutputCollection,
+      routing: {
+        mode: "fixed",
+        collection: wf.kbOutputCollection
+      },
       nameTemplate: wf.kbOutputTemplate.nameTemplate,
-      descriptionField: wf.kbOutputTemplate.descriptionField
+      descriptionField: wf.kbOutputTemplate.descriptionField,
+      descriptionSource: "final-output-text"
     } : null;
     if (!summaryCapture) {
       return validationResult(
@@ -3756,7 +3769,12 @@ This checkpoint was NOT saved. The conversation context is preserved \u2014 cont
         finalRoundId: roundId,
         finalOutput: normalizedOutput,
         summaryCapture: {
-          collection: summaryCapture.collection,
+          routing: summaryCapture.routing.mode === "fixed" ? {
+            mode: "fixed",
+            collection: summaryCapture.routing.collection
+          } : {
+            mode: "classifier"
+          },
           nameTemplate: summaryCapture.nameTemplate,
           descriptionField: summaryCapture.descriptionField,
           descriptionSource: summaryCapture.descriptionSource
@@ -3766,7 +3784,7 @@ This checkpoint was NOT saved. The conversation context is preserved \u2014 cont
       });
       lines.push(
         result.summary.created ? `**Draft Created**: \`${result.summary.entryId}\`` : `**Draft Already Exists**: \`${result.summary.entryId}\``,
-        `Collection: \`${summaryCapture.collection}\``,
+        `Collection: \`${result.summary.collection ?? (summaryCapture.routing.mode === "fixed" ? summaryCapture.routing.collection : "classifier-routed")}\``,
         `Name: ${result.summary.name}`,
         "",
         `The summary is captured as a draft. Use \`commit-entry entryId="${result.summary.entryId}"\` to promote it to the Chain.`,
@@ -3780,7 +3798,7 @@ This checkpoint was NOT saved. The conversation context is preserved \u2014 cont
             entryId: result.summary.entryId,
             workflowId,
             roundId,
-            collection: summaryCapture.collection,
+            collection: result.summary.collection ?? (summaryCapture.routing.mode === "fixed" ? summaryCapture.routing.collection : null),
             isFinal: true,
             runId: result.runId,
             created: result.summary.created
@@ -3804,9 +3822,9 @@ This checkpoint was NOT saved. The conversation context is preserved \u2014 cont
       lines.push(
         `**Chain commit failed**: ${msg}`,
         "",
-        `The retro output is preserved in this conversation. `,
+        `The workflow output is preserved in this conversation. `,
         `You can manually create the entry later using \`capture\` with:`,
-        `- Collection: \`${summaryCapture.collection}\``,
+        `- Collection: \`${summaryCapture.routing.mode === "fixed" ? summaryCapture.routing.collection : "classifier-routed"}\``,
         `- Name: ${summaryName ?? summaryCapture.nameTemplate}`,
         `- Description: ${summaryDescription ?? outputPreview}`
       );
@@ -6058,7 +6076,7 @@ async function handleCommitConstellation(args) {
   }
   let contradictionWarnings = [];
   try {
-    const { runContradictionCheck } = await import("./smart-capture-3OXWEXWM.js");
+    const { runContradictionCheck } = await import("./smart-capture-6IM4EMLF.js");
     const descField = betData.problem ?? betData.description ?? "";
     contradictionWarnings = await runContradictionCheck(
       betEntry.name ?? betId,
@@ -10877,7 +10895,7 @@ Make sure the rule is consistent with existing rules and doesn't contradict them
   );
   server.prompt(
     "run-workflow",
-    "Launch a Chainwork workflow (retro, shape, IDM) in Facilitator Mode. Returns the full workflow definition, facilitation instructions, and round structure. The agent enters Facilitator Mode and guides the participant through each round.",
+    "Launch any registered Chainwork workflow in Facilitator Mode. Returns the full workflow definition, facilitation instructions, and round structure. The agent enters Facilitator Mode and guides the participant through each round.",
     {
       workflow: z21.string().describe(
         "Workflow ID to run. Available: " + listWorkflows().map((w) => `'${w.id}' (${w.name})`).join(", ")
@@ -10943,13 +10961,17 @@ Use it \u2014 don't make them repeat themselves.
 ` : "";
       const outputDescription = descriptor ? describeWorkflowPrimaryOutput(descriptor) : wf.kbOutputCollection ? `Primary record routes to \`${wf.kbOutputCollection}\`.` : "Primary output routing is resolved at runtime.";
       const summaryCapture = descriptor ? getWorkflowSummaryCaptureDefinition(descriptor) : wf.kbOutputCollection && wf.kbOutputTemplate ? {
-        collection: wf.kbOutputCollection,
+        routing: {
+          mode: "fixed",
+          collection: wf.kbOutputCollection
+        },
         nameTemplate: wf.kbOutputTemplate.nameTemplate,
-        descriptionField: wf.kbOutputTemplate.descriptionField
+        descriptionField: wf.kbOutputTemplate.descriptionField,
+        descriptionSource: "final-output-text"
       } : null;
-      const chainOutputBlock = summaryCapture ? `Primary record routes to \`${summaryCapture.collection}\`.
+      const chainOutputBlock = summaryCapture ? `Primary record routes to \`${summaryCapture.routing.mode === "fixed" ? summaryCapture.routing.collection : "classifier"}\`.
 Summary capture template: ${summaryCapture.nameTemplate}
-Description field: ${summaryCapture.descriptionField}
+Description field: ${summaryCapture.descriptionField ?? "collection default"}
 ` : `Primary output: ${outputDescription}
 Use the workflow guidance to capture the primary record directly rather than relying on final summary auto-capture.
 `;
@@ -11596,4 +11618,4 @@ export {
   SERVER_VERSION,
   createProductBrainServer
 };
-//# sourceMappingURL=chunk-QUWYOGHB.js.map
+//# sourceMappingURL=chunk-HQLEMADT.js.map