@productbrain/mcp 0.0.1-beta.51 → 0.0.1-beta.52

package/dist/{chunk-LHDBWH6M.js → chunk-SCSEEERT.js}

@@ -2949,7 +2949,7 @@ var IMPLEMENTATION_REVIEW_WORKFLOW = {
 - \`verify\` \u2014 glossary code mappings, cross-references vs codebase
 - \`review-against-rules\` (domain) \u2014 business rule compliance
 - \`context action=gather task="implementation review for [BET-ID]"\` \u2014 related knowledge
-- Context7 \`query-docs\` \u2014 Vitest, Convex, Node.js best practices (resolve-library-id first)
+- Context7 \`query-docs\` \u2014 relevant testing and framework best practices (resolve-library-id first)
 - \`session-wrapup\` \u2014 before close
 
 ## Sub-Agent Classification (for test failures)
@@ -2990,7 +2990,7 @@ When reviewing test results: (a) test staleness \u2014 code changed, test not up
       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 Vitest/Convex best practices if needed. Classify any test failures: staleness, regression, or flaky. Synthesize: implementation grade, test honesty verdict, refactoring suggestions.",
+      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.",
       outputSchema: {
         field: "codeAndTests",
         description: "Implementation grade, test honesty, refactor suggestions",
@@ -3045,7 +3045,7 @@ When reviewing test results: (a) test staleness \u2014 code changed, test not up
   kbOutputCollection: "insights",
   kbOutputTemplate: {
     nameTemplate: "Implementation Review: {scope} \u2014 {date}",
-    descriptionField: "rationale"
+    descriptionField: "description"
   },
   errorRecovery: `If anything goes wrong during implementation review:
 
@@ -3088,11 +3088,7 @@ var PROCESS_CHANGE_WORKFLOW = {
 - **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.
-- **Show what you captured.** Always confirm what went to the Chain before closing.
-
-## Error Recovery
-
-If any tool fails: explain briefly, capture in conversation, offer to retry later. The workflow must never block the user's real work.`,
+- **Show what you captured.** Always confirm what went to the Chain before closing.`,
   rounds: [
     {
       id: "orient",
@@ -11049,4 +11045,4 @@ export {
   SERVER_VERSION,
   createProductBrainServer
 };
-//# sourceMappingURL=chunk-LHDBWH6M.js.map
+//# sourceMappingURL=chunk-SCSEEERT.js.map