pipebrain-mcp 0.27.0 → 0.28.0

package/dist/main.js

@@ -16600,7 +16600,7 @@ var ApiClient = class _ApiClient {
   // --- the waiting queue -----------------------------------------------------
   /**
    * Every gate awaiting a person across ALL projects of the caller's organisation
-   * (PIPE-87): revisions awaiting approval, questions awaiting an answer, and epics
+   * (PIPE-87): revisions awaiting approval, questions awaiting an answer, and work
    * in `verify` with a criterion not yet passed, longest wait first.
    *
    * Takes NO project and NO org: a queue you point at a project is the per-project
@@ -17014,7 +17014,7 @@ Every loose end has one destination, and none of them is prose. Anything you not
     }
   }, (args) => run(() => client2.createProject(args)));
   registerTool("list_waiting", {
-    description: "Every gate awaiting a PERSON across ALL projects in the token\u2019s org, longest wait first: a requirement revision awaiting approval, a question awaiting an answer, and an epic in `verify` holding at least one criterion not yet passed. Each entry names its project, the ref the action is taken on (`KEY-R{n}` for a revision, the ISSUE\u2019s `KEY-{n}` for a question or an epic), and `waitingSince` \u2014 the instant the wait began, not a duration. Nothing else is a gate: work in `triage` never appears, and neither does an epic in verify whose criteria have ALL passed. READ-ONLY, and there is no tool on this surface that clears any of the three \u2014 approving a revision, answering a question and marking a manual criterion are all decisions a person takes in the web app. Use it to see what your work is blocked on before asking, rather than to act on it."
+    description: "Every gate awaiting a PERSON across ALL projects in the token\u2019s org, longest wait first: a requirement revision awaiting approval, a question awaiting an answer, and work in `verify` holding at least one criterion not yet passed. Each entry names its project, the ref the action is taken on (`KEY-R{n}` for a revision, the ISSUE\u2019s `KEY-{n}` for a question or for work at verify), and `waitingSince` \u2014 the instant the wait began, not a duration. Nothing else is a gate: work in `triage` never appears, and neither does work in verify whose criteria have ALL passed. READ-ONLY, and there is no tool on this surface that clears any of the three \u2014 approving a revision, answering a question and marking a manual criterion are all decisions a person takes in the web app. Use it to see what your work is blocked on before asking, rather than to act on it."
     // NO arguments — not even an org. Org scope arrives from the token, exactly as
     // it does for `list_projects`, and an org parameter would open a cross-org read
     // path that has no precedent anywhere on this surface. The viewer narrowing the
@@ -17459,7 +17459,7 @@ function loadMcpConfig() {
 }
 
 // src/version.ts
-var VERSION = "0.27.0";
+var VERSION = "0.28.0";
 
 // src/main.ts
 var config2 = loadMcpConfig();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pipebrain-mcp",
-  "version": "0.27.0",
+  "version": "0.28.0",
   "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",