pipebrain-mcp 0.36.0 → 0.37.1

package/dist/main.js

@@ -15104,6 +15104,9 @@ var requirementRefSchema = external_exports.string().min(1, {
 var conventionRefSchema = external_exports.string().min(1, {
   message: "convention reference must not be empty \u2014 use a display id (`CONV-3`) or uuid"
 });
+var promptRefSchema = external_exports.string().min(1, {
+  message: "prompt reference must not be empty \u2014 use a display id (`PROMPT-3`) or uuid"
+});
 var decisionRefSchema = external_exports.string().min(1, {
   message: "decision reference must not be empty \u2014 use a display id (`DWB-D7`) or uuid"
 });
@@ -15445,6 +15448,29 @@ var conventionApprovalSchema = external_exports.object({
   supersededId: uuidSchema.nullable(),
   createdAt: external_exports.iso.datetime({ offset: true })
 });
+var promptSchema = external_exports.object({
+  id: uuidSchema,
+  displayId: external_exports.string().min(1),
+  orgId: uuidSchema,
+  number: positiveIntSchema,
+  projectId: uuidSchema.nullable(),
+  createdBy: uuidSchema.nullable(),
+  createdAt: external_exports.iso.datetime({ offset: true }),
+  updatedAt: external_exports.iso.datetime({ offset: true }),
+  deletedAt: external_exports.iso.datetime({ offset: true }).nullable()
+});
+var promptRevisionSchema = external_exports.object({
+  id: uuidSchema,
+  orgId: uuidSchema,
+  promptId: uuidSchema,
+  revisionNumber: positiveIntSchema,
+  title: external_exports.string().min(1),
+  body: markdownSchema,
+  note: external_exports.string().nullable(),
+  createdBy: uuidSchema.nullable(),
+  viaTokenId: uuidSchema.nullable(),
+  createdAt: external_exports.iso.datetime({ offset: true })
+});
 var issueRequirementLinkSchema = external_exports.object({
   id: uuidSchema,
   orgId: uuidSchema,
@@ -15909,6 +15935,32 @@ var updateConventionInputSchema = external_exports.strictObject({
 var listConventionsFilterSchema = external_exports.strictObject({
   text: external_exports.string().optional()
 });
+var createPromptInputSchema = external_exports.strictObject({
+  title: external_exports.string().min(1, { message: "prompt title must not be empty" }),
+  body: markdownSchema.min(1, { message: "prompt body must not be empty" }),
+  note: external_exports.string().min(1, { message: "note must not be empty \u2014 omit it if there is nothing to record" }).optional(),
+  // The OPTIONAL project attachment. Omitted = a prompt that belongs to the organisation
+  // and no project, which is the common case for a prompt about how to work.
+  project: projectRefSchema.optional()
+});
+var updatePromptInputSchema = external_exports.strictObject({
+  prompt: promptRefSchema,
+  title: external_exports.string().min(1, { message: "prompt title must not be empty" }).optional(),
+  body: markdownSchema.min(1, { message: "prompt body must not be empty" }).optional(),
+  note: external_exports.string().min(1, { message: "note must not be empty \u2014 omit it if there is nothing to record" }).optional(),
+  // `null` DETACHES the prompt from its project; omitted leaves the attachment alone.
+  // Moving the attachment is a record-level change and writes NO revision — the
+  // revision chain is the history of the text, and a project move changes no text.
+  project: projectRefSchema.nullable().optional()
+}).refine((v) => v.title !== void 0 || v.body !== void 0 || v.project !== void 0, {
+  message: "empty edit: supply at least one of `title`, `body`, or `project`"
+});
+var listPromptsFilterSchema = external_exports.strictObject({
+  // Filters to prompts attached to this project. Omitted returns EVERY prompt in the
+  // organisation, attached or not — the org-wide library is the default view.
+  project: projectRefSchema.optional(),
+  text: external_exports.string().optional()
+});
 var createDecisionInputSchema = external_exports.strictObject({
   project: projectRefSchema,
   title: external_exports.string().min(1, { message: "decision title must not be empty" }),
@@ -16517,6 +16569,44 @@ var ApiClient = class _ApiClient {
       body: fields
     });
   }
+  // --- prompts (PIPE-196) ----------------------------------------------------
+  //
+  // FOUR methods, and the absence of a fifth is the design here too: there is deliberately
+  // NO `deletePrompt`, and there must not be one. Nothing removes a prompt on any surface
+  // — an edit APPENDS a revision, so the text a prompt used to carry stays readable, and a
+  // prompt nobody runs any more is one whose newest revision says so. There is no route
+  // for such a method to call.
+  /**
+   * The whole organization's library, filtered by `project` and/or `text`.
+   *
+   * `requestList`, like every other list on this client, and NOT {@link listConventions}'s
+   * named object: the convention response is a bespoke envelope because it carries the
+   * delivered count and the threshold that warns about it beside the list — every approved
+   * convention rides along on every work-item read. A prompt is delivered to nobody
+   * automatically, so there is no second number to carry and the plain §9 `{ items }`
+   * envelope is the whole shape. Going through `requestList` is what turns a proxy's
+   * malformed 2xx into a typed `invalid_response` here rather than an opaque TypeError at
+   * whichever caller first maps the result.
+   */
+  listPrompts(filter = {}) {
+    return this.requestList("GET", "/api/v1/prompts", { query: filter });
+  }
+  getPrompt(ref) {
+    return this.request("GET", `/api/v1/prompts/${enc(ref)}`);
+  }
+  createPrompt(input) {
+    return this.request("POST", "/api/v1/prompts", { body: input });
+  }
+  /**
+   * `title`/`body` APPEND a revision; `note` records why. Supplying none of the three
+   * editable fields is an empty edit, refused by the API (400) — a note alone amends
+   * nothing.
+   */
+  updatePrompt(ref, fields) {
+    return this.request("PATCH", `/api/v1/prompts/${enc(ref)}`, {
+      body: fields
+    });
+  }
   // --- decision records (PIPE-84) --------------------------------------------
   //
   // Five routes, no DELETE: PIPE-73 made four record kinds deletable and this epic
@@ -17358,7 +17448,7 @@ function createMcpServer(client2, apiBaseUrl, orgInstructions2 = /* @__PURE__ */
     inputSchema: createIssueInputSchema.shape
   }, (args) => run(() => client2.createIssue(args)));
   server2.registerTool("promote_feedback", {
-    description: "Promote a FEEDBACK issue into a NEW epic or task (PIPE-143): creates the issue in the feedback\u2019s project (`title` + `type` required; omitted environment inherits the FEEDBACK\u2019s environment, not the project default; optional status/body/priority/milestone/requirement_links/criteria as in create_issue), records the feedback as its permanent source (`promotedFrom`/`promotedTo` on both details), closes the feedback as done, and comments the new key on it. The feedback\u2019s own title/body are never touched \u2014 write the new issue\u2019s body as real work. Rejected (409) for non-feedback, terminal, or already-promoted sources. Returns the created issue. A `status` other than `triage` or `killed` REQUIRES `milestone` (PIPE-R10 rule 9), exactly as in create_issue; the SOURCE feedback needs none to be closed by the promotion. A `manual` criterion must carry `howTo` \u2014 one or two sentences saying where to look, what to do, and what counts as passing; writing or changing one without it is refused (`how_to_required`), and so is supplying it on an `auto` criterion, which a machine checks. Work of any kind carries criteria \u2014 an epic, a task, a bug alike \u2014 with feedback the one exception, refused with `criteria_not_supported` because it is a report rather than agreed work; this tool is what retypes it into work before anything is built. Writing guidance for this tool lives in the product doctrine, which `get_work_context` returns \u2014 see \u201CSearch before you create\u201D and \u201CThe bar for filing a bug\u201D.",
+    description: "Promote a FEEDBACK issue into a NEW epic or task (PIPE-143): creates the issue in the feedback\u2019s project (`title` + `type` required; omitted environment inherits the FEEDBACK\u2019s environment, not the project default; optional status/body/priority/milestone/requirement_links/criteria as in create_issue), records the feedback as its permanent source (`promotedFrom`/`promotedTo` on both details), closes the feedback as done, and comments the new key on it. The feedback\u2019s own title/body are never touched \u2014 write the new issue\u2019s body as real work. Rejected (409) for non-feedback, terminal, or already-promoted sources, and refused (422 `status_guard`, naming each offending child and its status) when the feedback carries a child issue that is not yet `done` or `killed` \u2014 closing the source would strand that child under a finished parent, so finish or kill the child first. Returns the created issue. A `status` other than `triage` or `killed` REQUIRES `milestone` (PIPE-R10 rule 9), exactly as in create_issue; the SOURCE feedback needs none to be closed by the promotion. A `manual` criterion must carry `howTo` \u2014 one or two sentences saying where to look, what to do, and what counts as passing; writing or changing one without it is refused (`how_to_required`), and so is supplying it on an `auto` criterion, which a machine checks. Work of any kind carries criteria \u2014 an epic, a task, a bug alike \u2014 with feedback the one exception, refused with `criteria_not_supported` because it is a report rather than agreed work; this tool is what retypes it into work before anything is built. Writing guidance for this tool lives in the product doctrine, which `get_work_context` returns \u2014 see \u201CSearch before you create\u201D and \u201CThe bar for filing a bug\u201D.",
     inputSchema: {
       issue: external_exports.string().min(1),
       ...promoteFeedbackInputSchema.shape
@@ -17506,6 +17596,33 @@ function createMcpServer(client2, apiBaseUrl, orgInstructions2 = /* @__PURE__ */
       note: external_exports.string().min(1).optional()
     }
   }, ({ convention, ...fields }) => run(() => client2.updateConvention(convention, fields)));
+  server2.registerTool("list_prompts", {
+    description: "List this organization\u2019s prompt library \u2014 reusable prompt text, addressed `PROMPT-{n}`. A prompt belongs to the ORGANIZATION rather than to a project, unlike a requirement or a content draft, so with no filter this returns the whole library. Returns display id, title, the current text, the latest revision number, and the attached project when it has one. `project` narrows to the prompts attached to that project \u2014 that attachment is metadata saying what a prompt is ABOUT, never its scope, so a prompt attached elsewhere is still one you may read and run. `text` matches over TITLE AND BODY, because someone looking for a prompt remembers what it says rather than what somebody called it.",
+    inputSchema: listPromptsFilterSchema.shape
+  }, (args) => run(() => client2.listPrompts(args), GUIDANCE_POINTER));
+  server2.registerTool("get_prompt", {
+    description: "Get one prompt by display id (`PROMPT-{n}`) or uuid: its current text \u2014 the LATEST revision, which is simply the prompt, since nothing approves a prompt and nothing pins to an older wording \u2014 plus the full revision history with who wrote each save, through which token, when, and the note saying why. Nothing here was edited in place, so a wording that has been replaced is still readable rather than lost; read the history before rewriting a prompt that already works.",
+    inputSchema: { prompt: promptRefSchema }
+  }, (args) => run(() => client2.getPrompt(args.prompt), GUIDANCE_POINTER));
+  server2.registerTool("create_prompt", {
+    description: "Write a prompt: reusable prompt text kept ORGANIZATION-WIDE (`PROMPT-{n}`) and available in every project here \u2014 unlike a requirement or a content draft, which belong to the one project they are filed under. `body` is the prompt itself and must not be empty; `title` names it; optional `note` records why it was written. Optional `project` ATTACHES the prompt to a project, which says what it is about and nothing more \u2014 the prompt is still the organization\u2019s, and a prompt about no project in particular simply omits it. There is no approval step: it is usable the moment it is written. Nothing deletes a prompt either \u2014 later wording is added as a revision, so what is here now stays readable. Writing guidance for this tool lives in the product doctrine, which `get_work_context` returns \u2014 see \u201CSearch before you create\u201D.",
+    inputSchema: createPromptInputSchema.shape
+  }, (args) => run(() => client2.createPrompt(args)));
+  server2.registerTool("update_prompt", {
+    description: "Amend a prompt: `title` and/or `body` APPEND a new revision \u2014 nothing is ever edited in place \u2014 and optional `note` records why. Amending is therefore safe rather than destructive: the earlier text stays readable, the revision chain is the record of how this prompt got to where it is, and the new wording answers immediately because there is nothing to approve. `project` moves the attachment and `project: null` DETACHES it, leaving a prompt the whole organization still has; either way NO revision is written, because the revision chain is the history of the TEXT and moving the attachment changes no text. Supplying none of `title`, `body` or `project` is an empty edit (400) \u2014 a note alone amends nothing.",
+    // Inline shape (updatePromptInputSchema is a refine, so it has no `.shape`),
+    // mirroring that schema's fields — it is the wording this copy follows, `.min(1)`
+    // bounds included, so a caller learns a blank body is refused from the advertised
+    // schema rather than from a round trip. The ONE rule this shape cannot state is the
+    // empty edit, which lives in the schema's `.refine`; the API enforces it.
+    inputSchema: {
+      prompt: promptRefSchema,
+      title: external_exports.string().min(1).optional(),
+      body: markdownSchema.min(1).optional(),
+      note: external_exports.string().min(1).optional(),
+      project: projectRefSchema.nullable().optional()
+    }
+  }, ({ prompt, ...fields }) => run(() => client2.updatePrompt(prompt, fields)));
   server2.registerTool("create_decision", {
     description: "Record ONE decision as a project-scoped decision record (`KEY-D{n}`): `title` names the decision and `body` says what was decided and why. A new record starts `proposed`; moving it to `accepted` IS the acceptance \u2014 there is no separate approval step. Returns the created record. Title and body can be corrected only while the record is `proposed`; from `accepted` onward it is frozen, and the way to change a decision is to write a NEW record and `supersede_decision` the old one \u2014 which leaves the original readable and says where the current decision went. Nothing on any surface deletes one. Writing guidance for this tool lives in the product doctrine, which `get_work_context` returns \u2014 see \u201CA decision record is written once\u201D and \u201CSearch before you create\u201D.",
     inputSchema: createDecisionInputSchema.shape
@@ -17716,7 +17833,7 @@ function loadMcpConfig() {
 }
 
 // src/version.ts
-var VERSION = "0.36.0";
+var VERSION = "0.37.1";
 
 // src/main.ts
 var config2 = loadMcpConfig();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pipebrain-mcp",
-  "version": "0.36.0",
+  "version": "0.37.1",
   "description": "Pipebrain MCP server for Claude Code and Claude Desktop — issues, requirements, content, assets, and metadata-only secrets over the Pipebrain API.",
   "type": "module",
   "license": "MIT",