@productbrain/mcp 0.0.1-beta.8543 → 0.0.1-beta.8546

package/dist/{chunk-NKK5TZHB.js → chunk-HM2EEYVT.js}

@@ -2850,7 +2850,7 @@ function pushAppliedFieldsLines(responseLines, fieldsProvided, appliedFields, re
 // src/tools/knowledge/getHistory.ts
 import { z as z5 } from "zod/v3";
 var getHistorySchema = z5.object({
-  entryId: z5.string().describe("Entry ID, e.g. 'T-SUPPLIER', '<PREFIX>-<n>'")
+  entryId: z5.string().describe("Entry ID, e.g. '<PREFIX>-<n>'")
 });
 async function handleGetHistory({ entryId }) {
   const history = await kernelQuery("chain.listEntryHistory", { entryId });
@@ -2881,7 +2881,7 @@ ${formatted}` }],
 
 // src/tools/knowledge.ts
 var updateEntrySchema = z6.object({
-  entryId: z6.string().describe("Entry ID to update, e.g. 'T-SUPPLIER', '<PREFIX>-<n>'"),
+  entryId: z6.string().describe("Entry ID to update, e.g. '<PREFIX>-<n>'"),
   name: z6.string().optional().describe("New display name"),
   // Chain-ID-leak guard (check:chain-id-leaks): the retired legacy-shim ticket number stays in
   // the code comment above, never in this user-visible describe() string. T8 (TASK-393, WP-779): narrowed to generated ENTRY_STATUS_WRITE_WORDS.
@@ -14304,7 +14304,7 @@ ${glossaryContext}
 
 For each name:
 1. Does it match a canonical term? If so, which one?
-2. Is there terminology drift? (e.g. using "vendor" instead of "supplier", "compliance" instead of "conformance")
+2. Is there terminology drift? (e.g. using "customer" instead of "member", "owner" instead of "admin")
 3. Suggest the canonical alternative if drift is detected.
 4. Flag any names that don't have a corresponding glossary term (might need one).
 
@@ -14324,20 +14324,20 @@ function registerPrompts(server) {
   server.prompt(
     "name-check",
     "Check variable names, field names, or API names against the glossary for terminology alignment. Flags drift from canonical terms.",
-    { names: z33.string().describe("Comma-separated list of names to check (e.g. 'vendor_id, compliance_level, formulator_type')") },
+    { names: z33.string().describe("Comma-separated list of names to check (e.g. 'user_id, workspace_id, entry_status')") },
     async ({ names }) => buildNameCheckPrompt(names)
   );
   server.prompt(
     "draft-decision-record",
     "Draft a structured decision record from a description of what was decided. Includes context from recent decisions and relevant rules.",
-    { context: z33.string().describe("Description of the decision (e.g. 'We decided to use MRSL v3.1 as the conformance baseline because...')") },
+    { context: z33.string().describe("Description of the decision (e.g. 'We decided to keep one body field per entry because...')") },
     async ({ context }) => buildDraftDecisionRecordPrompt(context)
   );
   server.prompt(
     "draft-rule-from-context",
     "Draft a new business rule from an observation or discovery made while coding. Fetches existing rules for the domain to ensure consistency.",
     {
-      observation: z33.string().describe("What you observed or discovered (e.g. 'Suppliers can have multiple org types in Gateway')"),
+      observation: z33.string().describe("What you observed or discovered (e.g. 'A workspace can have more than one owner role')"),
       domain: z33.string().describe("Which domain this rule belongs to (e.g. 'Governance & Decision-Making')")
     },
     async ({ observation, domain }) => buildDraftRuleFromContextPrompt(observation, domain)
@@ -14525,4 +14525,4 @@ export {
   createProductBrainServer,
   initFeatureFlags
 };
-//# sourceMappingURL=chunk-NKK5TZHB.js.map
+//# sourceMappingURL=chunk-HM2EEYVT.js.map