@productbrain/mcp 0.0.1-beta.4600 → 0.0.1-beta.4603

package/dist/{chunk-3FK3GMB5.js → chunk-O222BPC6.js}

@@ -10709,7 +10709,7 @@ Use \`workflows action=checkpoint\` after each round to persist progress to the
       label: "Validate & Build Contract",
       type: "synthesis",
       instruction: "Check completeness. Generate the build contract. Review the full scorecard.",
-      facilitatorGuidance: "Review the scorecard from the shaping skill's scoring rubric. Present it as a table. Verify the 5 core ingredients: Problem, Appetite, Solution elements, Rabbit Holes, No-Gos. For Big Batch: also verify Architecture, narrative hook, and value-flow annotations. **System coherence confirmation:** Were all five paths traced for each element? State which interaction risks remain unverified \u2014 these become explicit risks in the work package, not surprises during implementation. **Vision narrative (TEN-281):** Write one paragraph \u2014 how does this bet serve the product vision? **Test plan (TEN-281):** How will we know this is done? Concrete scenarios, not 'when tests pass.' **Counter-Metric Mandate (STD-19):** If the scorecard or build contract contains metrics or gates, verify each has a denominator, a coverage rate, and a counter-metric. Flag any gate that can be satisfied by abstaining or excluding the hard cases. Present the build contract. Ask: 'Anything to adjust before we capture to the Chain?'",
+      facilitatorGuidance: "Review the scorecard from the shaping skill's scoring rubric. Present it as a table. Verify the 5 core ingredients: Problem, Appetite, Solution elements, Rabbit Holes, No-Gos. For Big Batch: also verify Architecture, narrative hook, and value-flow annotations. **System coherence confirmation:** Were all five paths traced for each element? State which interaction risks remain unverified \u2014 these become explicit risks in the work package, not surprises during implementation. **Vision narrative (TEN-281):** Write one paragraph \u2014 how does this work package serve the product vision? **Test plan (TEN-281):** How will we know this is done? Concrete scenarios, not 'when tests pass.' **Counter-Metric Mandate (STD-19):** If the scorecard or build contract contains metrics or gates, verify each has a denominator, a coverage rate, and a counter-metric. Flag any gate that can be satisfied by abstaining or excluding the hard cases. Present the build contract. Ask: 'Anything to adjust before we capture to the Chain?'",
       outputSchema: {
         field: "validation",
         description: "Completeness check result and build contract",
@@ -17048,4 +17048,4 @@ export {
   createProductBrainServer,
   initFeatureFlags
 };
-//# sourceMappingURL=chunk-3FK3GMB5.js.map
+//# sourceMappingURL=chunk-O222BPC6.js.map