pipebrain-mcp 0.29.0 → 0.31.0

package/dist/main.js

@@ -429,6 +429,9 @@ function apiBindingLabel(apiBaseUrl) {
   return /\/\/(localhost|127\.0\.0\.1|0\.0\.0\.0|\[::1\])(:|\/|$)/.test(apiBaseUrl) ? "LOCAL dev" : "production/remote";
 }
 
+// ../../libs/agent-shared/dist/doctrine.js
+var DOCTRINE = "# Pipebrain doctrine\n\nHow an agent works inside Pipebrain. These rules ship with the product and read the same in every organization, because each exists where disagreeing breaks something the product guarantees rather than merely changing house style.\n\nHow your organization *writes* is its own text, edited in Settings, and follows this document under a heading naming each scope.\n\n## Decisions are yours; escalate on consequence\n\nInside an approved requirement you choose the design, the libraries, the structure, and the sequencing. Do not ask, report, or seek ratification for the choice. Escalate on consequence, not uncertainty: a choice that changes what a user sees, costs money, or contradicts an approved requirement is filed as a question with the options you propose; everything else you decide and carry on. A technical choice worth keeping is a decision record, never a paragraph.\n\n## Every loose end has one destination, and none of them is prose\n\nAnything you notice that is not the work in front of you goes to exactly one of three places: a question, when the operator has to choose; a new issue at triage, when it is real work outside this item's scope; or nowhere. Nowhere is the default, and the right outcome whenever knowing the thing would change nothing anyone does. Never open a section called notes, caveats, observations, things to know, or next steps in a body or a comment. Filing is the report: an item recorded and then repeated in prose asks the operator to triage it twice.\n\n## A decision you need is filed as a question, never written into a body\n\nAn open decision belongs in a question on the issue, filed with `ask_questions`, carrying the options you propose. It does not belong in a body \u2014 not under a heading, and not in a field. A decision written into prose prompts nobody and records no answer, so the operator has no place to make it and a later session cannot tell whether it ever was. Retract one your own work has since settled, so nothing asks the operator to decide something nobody waits on.\n\n## Search before you create\n\nLook for the existing record before adding one. A duplicate splits one thing's history across two identifiers, and the split is permanent \u2014 nothing merges them afterward.\n\n## Link by key; never paste another record's text\n\nReference a requirement, a decision, or an issue by its key, with its title on first mention. Never paste its text into a body. The source changes and the copy does not, and the stale copy is what gets built.\n\n## Cross-cutting requirements arrive on their own\n\nThey bind every epic automatically and come back with a work-item read, at their latest approved revision. Never restate them in a body and never add them as explicit requirement links. An explicit link pins a document at an approved revision, which is a different act.\n\n## Verification modes follow what can be driven\n\nBefore assigning a mode, establish what this project can drive end to end: a harness, and the command that runs it. A criterion is `auto` when an evaluator can drive the input and read the result against the running system, including behavior shown in an interface wherever such a harness exists. What qualifies it is the evaluator's own run, never the existence of a test the implementer wrote.\n\nMark `manual` only when the verdict needs a person's judgment. A criterion you cannot describe as drivable is usually worded too vaguely: reword it against the observable rather than fall back to a person. A `manual` criterion carries instructions for whoever checks it by hand, written for someone who has not seen the code or the conversation that produced it.\n\nA manual criterion carrying no recorded artifact is the human gate working as designed rather than a coverage gap, so it is neither a finding nor weaker than one carrying evidence.\n\n## The bar for filing a bug\n\nFile a bug only when the observed behavior breaks an approved requirement or a defined acceptance criterion, and name which one before you file. Failing that, it is not a bug: code you find unclear, an edge case nobody specified, a performance number nobody set, and anything you would phrase as \"this could be better\" are opinions about the product, so file each as feedback or not at all. The bar exists because a queue holding both real defects and unshared taste has to be read entirely before any of it can be trusted.\n\n## A decision record is written once\n\nIt states what was decided and why, at the time it was decided, and is not edited as understanding moves. A superseding record replaces it, and the chain of the two is the account of how the thinking changed \u2014 which an edited record destroys. Read the existing records before re-opening a settled question.\n\n## A secret value never travels in a tool call\n\nNo tool here returns one, and that is deliberate rather than an omission to be fixed. Nor should you put one in: a value typed into a tool call is in the transcript before the server can encrypt it, so it is already disclosed and the only remedy left is rotation. Set values with the command-line tool, from a file or on standard input, and inject them at run time rather than reading them into context.\n\n## Setting an instruction replaces the whole body\n\nThere is no partial update. Writing an instruction stores exactly the body you supply and discards everything that was there, so a partial write destroys the rest of the text. The procedure is: read the live value, compose the complete replacement, write it, then read the live value again to confirm what landed.\n\nWhat you are reading now is a snapshot taken when this session started, and so are the tool descriptions. An edit reaches the next session, never this one, so reading the text back after a write shows the pre-edit value. An agent that reports a diff of what it just wrote has read the snapshot instead of the record.\n";
+
 // ../../libs/agent-shared/dist/resolve-agent-env.js
 function pick(env, primary, legacy) {
   const fromPrimary = env[primary];
@@ -15098,6 +15101,13 @@ var DisplayIdError = class extends Error {
 };
 var PROJECT_KEY = /^[A-Z]{2,5}$/;
 var DELIVERABLE_RE = /^([A-Z]{2,5})-C([1-9][0-9]*)\/([a-z0-9]+)$/;
+var INT4_MAX = 2147483647;
+function matchDisplayId(re, value, numberGroup) {
+  const match = re.exec(value);
+  if (match === null)
+    return null;
+  return Number(match[numberGroup]) > INT4_MAX ? null : match;
+}
 function assertKey(key) {
   if (!PROJECT_KEY.test(key)) {
     throw new DisplayIdError("project key must be 2\u20135 uppercase letters (A\u2013Z)", key);
@@ -15114,7 +15124,7 @@ function formatContentDisplayId(key, number4) {
   return `${key}-C${number4}`;
 }
 function parseDeliverableDisplayId(value) {
-  const match = DELIVERABLE_RE.exec(value);
+  const match = matchDisplayId(DELIVERABLE_RE, value, 2);
   if (match === null) {
     throw new DisplayIdError("not a valid deliverable display id (expected `KEY-C{N}/{platform}`)", value);
   }
@@ -15585,6 +15595,9 @@ var orgInstructionSchema = external_exports.object({
 });
 
 // ../../libs/domain/dist/inputs.js
+var int4Schema = positiveIntSchema.max(2147483647, {
+  message: "must be no greater than 2147483647"
+});
 var criterionInputSchema = external_exports.strictObject({
   text: markdownSchema.min(1, { message: "criterion text must not be empty" }),
   verification: verificationSchema.optional(),
@@ -15699,7 +15712,7 @@ var setCriteriaInputSchema = external_exports.strictObject({
 var setCriterionStateInputSchema = external_exports.strictObject({
   criterionId: uuidSchema.optional(),
   issue: issueRefSchema.optional(),
-  criterionNumber: positiveIntSchema.optional(),
+  criterionNumber: int4Schema.optional(),
   state: criterionStateSchema,
   evidence: markdownSchema.optional()
 }).refine((v) => {
@@ -15718,9 +15731,7 @@ var askQuestionsInputSchema = external_exports.strictObject({
   issue: issueRefSchema,
   questions: external_exports.array(questionInputSchema).min(1, { message: "ask at least one question" })
 });
-var questionNumberSchema = positiveIntSchema.max(2147483647, {
-  message: "question number is out of range"
-});
+var questionNumberSchema = int4Schema;
 var withdrawQuestionInputSchema = external_exports.strictObject({
   issue: issueRefSchema,
   number: questionNumberSchema
@@ -15755,7 +15766,8 @@ var updateRequirementInputSchema = external_exports.strictObject({
 });
 var approveRequirementInputSchema = external_exports.strictObject({
   requirement: requirementRefSchema,
-  revision: positiveIntSchema.optional()
+  // → requirement_revisions.revision_number, an `integer` column (PIPE-149).
+  revision: int4Schema.optional()
 });
 var createDecisionInputSchema = external_exports.strictObject({
   project: projectRefSchema,
@@ -15879,7 +15891,8 @@ var updateSecretDescriptionInputSchema = external_exports.strictObject({
 });
 var rollbackSecretInputSchema = external_exports.strictObject({
   env: external_exports.string().min(1, { message: "environment must not be empty" }),
-  version: positiveIntSchema
+  // → secret_versions.version, an `integer` column (PIPE-149).
+  version: int4Schema
 });
 var secretRefSchema = external_exports.strictObject({
   project: projectKeySchema,
@@ -15999,7 +16012,8 @@ var listAssetsFilterSchema = external_exports.strictObject({
 var createChatMessageReferenceInputSchema = external_exports.strictObject({
   entityType: chatEntityTypeSchema,
   entityId: uuidSchema,
-  revision: positiveIntSchema.optional()
+  // → requirement_revisions.revision_number, an `integer` column (PIPE-149).
+  revision: int4Schema.optional()
 });
 var createChatMessageInputSchema = external_exports.strictObject({
   body: external_exports.string().min(1, { message: "message body must not be empty" }).max(8e3, { message: "message body must be at most 8000 characters" }),
@@ -16029,32 +16043,6 @@ var deleteOrgInstructionInputSchema = external_exports.strictObject({
   scope: instructionScopeSchema
 });
 
-// ../../libs/domain/dist/instructions.js
-var ISSUE_WRITE_TOOLS = [
-  "create_issue",
-  "update_issue",
-  "promote_feedback",
-  "open_review"
-];
-var INSTRUCTION_SCOPE_TARGETS = {
-  general: { kind: "server" },
-  requirements: { kind: "tools", tools: ["create_requirement", "update_requirement"] },
-  content: {
-    kind: "tools",
-    tools: ["create_content", "update_content", "create_deliverable", "update_deliverable"]
-  },
-  "work.epic": { kind: "issue_tools", issueType: "epic", tools: ISSUE_WRITE_TOOLS },
-  "work.task": { kind: "issue_tools", issueType: "task", tools: ISSUE_WRITE_TOOLS },
-  "work.bug": { kind: "issue_tools", issueType: "bug", tools: ISSUE_WRITE_TOOLS },
-  "work.feedback": { kind: "issue_tools", issueType: "feedback", tools: ISSUE_WRITE_TOOLS }
-};
-function scopesForTool(tool) {
-  return instructionScopeSchema.options.filter((scope) => {
-    const target = INSTRUCTION_SCOPE_TARGETS[scope];
-    return target.kind !== "server" && target.tools.includes(tool);
-  });
-}
-
 // ../../libs/agent-shared/dist/token-shape.js
 function isAcceptedTokenShape(value) {
   return ACCEPTED_TOKEN_PREFIXES.some((prefix) => value.startsWith(prefix));
@@ -16889,7 +16877,7 @@ async function fetchOrgInstructionsSafe(client2) {
     return map2;
   } catch (err) {
     const message = err instanceof Error ? err.message : String(err);
-    process.stderr.write(`pipebrain mcp: org instructions unavailable (${message}) \u2014 starting with base tool descriptions
+    process.stderr.write(`pipebrain mcp: org instructions unavailable (${message}) \u2014 starting with the doctrine alone
 `);
     return /* @__PURE__ */ new Map();
   } finally {
@@ -16897,34 +16885,17 @@ async function fetchOrgInstructionsSafe(client2) {
       clearTimeout(timer);
   }
 }
-function decorateDescription(toolName, base, instructions) {
-  let out = base;
-  const kindLines = [];
-  for (const scope of scopesForTool(toolName)) {
+function composeGuidance(base, instructions) {
+  const blocks = [base, DOCTRINE.trim()];
+  for (const scope of instructionScopeSchema.options) {
     const body = instructions.get(scope);
     if (body === void 0)
       continue;
-    const target = INSTRUCTION_SCOPE_TARGETS[scope];
-    if (target.kind === "issue_tools") {
-      kindLines.push(`[${target.issueType}] ${body}`);
-    } else {
-      out += `
+    blocks.push(`## Organization instructions \u2014 ${scope}
 
-Org instructions (${scope}):
-${body}`;
-    }
-  }
-  if (kindLines.length > 0) {
-    out += "\n\nOrg instructions by issue `type` \u2014 apply ONLY the block matching the `type` you pass:\n\n" + kindLines.join("\n\n");
+${body}`);
   }
-  return out;
-}
-function withGeneralInstructions(base, instructions) {
-  const general = instructions.get("general");
-  return general === void 0 ? base : `${base}
-
-Org instructions:
-${general}`;
+  return blocks.join("\n\n");
 }
 
 // ../../libs/mcp-server/dist/server.js
@@ -16986,14 +16957,15 @@ async function resolveDeliverableTargetId(client2, projectKey, ref) {
 function createMcpServer(client2, apiBaseUrl, orgInstructions2 = /* @__PURE__ */ new Map(), opts = {}) {
   const surface = opts.surface ?? "local";
   const server2 = new McpServer({ name: "pipebrain", version: opts.version ?? DEFAULT_VERSION }, {
-    instructions: withGeneralInstructions(successorNotice() + `Pipebrain MCP server, bound to the ${apiBindingLabel(apiBaseUrl)} API at ${apiBaseUrl}. Every tool reads and writes THAT environment \u2014 confirm it is the one you intend (a local dev API vs production) before mutating. Tools are namespaced by this server's registration name in .mcp.json (e.g. pipebrain-local:* vs pipebrain:*).
-
-Technical decisions are yours. Inside an approved requirement you choose the design, the libraries, the structure, and the sequencing. Do not ask, do not report the choice, and do not seek ratification for it. Escalate on consequence, not on uncertainty: a choice that changes what a user sees, costs money, or contradicts an approved requirement is filed as a question with the options you propose, and everything else you decide and carry on. A technical choice worth keeping is recorded as a decision record, never as a paragraph.
-
-Every loose end has one destination, and none of them is prose. Anything you notice that is not the work in front of you goes to exactly one of three places: a question, when the operator has to choose; a new issue at triage, when it is real work outside this item\u2019s scope; or nowhere. Drop it unless it clears the bar for one of the first two \u2014 nowhere is the default, and it is the right outcome whenever knowing the thing would change nothing anyone does. Never open a section called notes, caveats, observations, things to know, or next steps in a body or a comment. Filing is the report: an item recorded and then repeated in prose asks the operator to triage it twice.`, orgInstructions2)
+    // The BASE is this server's own two facts — which package is speaking (only
+    // when the legacy wrapper arms the notice) and which environment it is bound
+    // to. Everything else a session is handed comes from `docs/DOCTRINE.md` and the
+    // org's saved texts, composed below. The two doctrine paragraphs that used to
+    // be written out here (PIPE-257, carrying decision record PIPE-D25) are now
+    // sections 1 and 2 of that file, so they are stated once and published.
+    instructions: composeGuidance(successorNotice() + `Pipebrain MCP server, bound to the ${apiBindingLabel(apiBaseUrl)} API at ${apiBaseUrl}. Every tool reads and writes THAT environment \u2014 confirm it is the one you intend (a local dev API vs production) before mutating. Tools are namespaced by this server's registration name in .mcp.json (e.g. pipebrain-local:* vs pipebrain:*).`, orgInstructions2)
   });
-  const registerTool = (name, config3, cb) => server2.registerTool(name, { ...config3, description: decorateDescription(name, config3.description ?? "", orgInstructions2) }, cb);
-  registerTool("list_projects", {
+  server2.registerTool("list_projects", {
     description: "List all projects with their key, environments, milestones (token, label, active), and open-issue counts \u2014 the project switcher and workflow entry point (\xA77).",
     // Optional pagination (§9) — bounds mirror list_issues/list_requirements; the
     // server defaults limit to 200 (max 500) and passes limit/offset as query params.
@@ -17002,7 +16974,7 @@ Every loose end has one destination, and none of them is prose. Anything you not
       offset: external_exports.number().int().nonnegative().optional()
     }
   }, (args) => run(() => client2.listProjects(args)));
-  registerTool("create_project", {
+  server2.registerTool("create_project", {
     description: "Create a new project \u2014 the workflow bootstrap entry point, since issues and requirements are all project-scoped and nothing can be filed until a project exists. Both `name` (its display label) and `key` are required; the key is 2\u20135 uppercase letters (A\u2013Z, e.g. `DWB`), unique per org, and becomes the prefix of every display id in the project. Returns the created project (\xA77).",
     // Inline shape: @pipeline/domain has no standalone create-project schema — the
     // same `{ name, key }` pair lives only inside createOrgInputSchema.project, so
@@ -17013,7 +16985,7 @@ Every loose end has one destination, and none of them is prose. Anything you not
       key: projectKeySchema
     }
   }, (args) => run(() => client2.createProject(args)));
-  registerTool("list_waiting", {
+  server2.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 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
@@ -17026,7 +16998,7 @@ Every loose end has one destination, and none of them is prose. Anything you not
     // makes that comparable at a glance.
     run(async () => ({ items: await client2.listWaiting() }))
   ));
-  registerTool("get_work_context", {
+  server2.registerTool("get_work_context", {
     description: "Everything a session needs before it starts work, in ONE read \u2014 assembled by the API and returned verbatim. Addressed by `issue` OR by `project`, never both and never neither: an issue names its own project, so the pair is refused rather than resolved for you (\xA77). Given an ISSUE: that issue\u2019s full detail \u2014 the same payload `get_issue` returns \u2014 PLUS the BODY TEXT of every requirement it links, AT THE REVISION THE LINK IS PINNED AT. That text is the round trip this removes: `get_issue` names which documents bind the work and at which revision, never what they SAY, so a session that has read the issue still owes one fetch per link \u2014 and the one it skips leaves it building against rules it never read. Comments come CAPPED at the newest `commentLimit`, with `commentCount` \u2014 the issue\u2019s TRUE total \u2014 beside them, so a shortened list reads AS shortened rather than as the whole history; read the issue directly for the rest. Given a PROJECT: `available`, the work a session could START right now. It EXCLUDES finished and abandoned work (`done`, `killed`), work another person has claimed, and anything blocked \u2014 the status guard would refuse to start that, and offering work that cannot be started is offering a refusal. Your OWN claims stay, and so does unscheduled work carrying no milestone. The item form carries no `available`; the project form carries no item. BOTH forms also carry the project half: the release currently being worked (the active milestone) and the project\u2019s cross-cutting requirements WITH their text \u2014 they bind every epic automatically, and each is otherwise a separate call a session can simply forget to make. READ-ONLY \u2014 this claims nothing, moves nothing and writes nothing. CALL IT when you begin a piece of work, or when you pick work up in a project \u2014 the whole pack, once, before you start. Read narrowly the rest of the time; that is the ordinary case and needs no justification.",
     // The WHOLE domain schema rather than its `.shape`: the exactly-one-of rule is a
     // refinement on the OBJECT, and a raw shape drops it — the SDK validates against
@@ -17035,7 +17007,7 @@ Every loose end has one destination, and none of them is prose. Anything you not
     // naming the two arguments it refused rather than a reworded stand-in.
     inputSchema: getWorkContextInputSchema
   }, (args) => run(() => client2.getWorkContext(args)));
-  registerTool("create_milestone", {
+  server2.registerTool("create_milestone", {
     description: "Create a milestone on a project. `token` is the short ref issues point at via their `milestone` field (e.g. `M1`) and is unique per project (a duplicate is rejected); `label` is its display name (e.g. `Feature Verification`). Optional `position` orders it (0-based, defaults to last); optional `active` marks it the current milestone \u2014 AT MOST ONE milestone per project is active, so `active: true` transactionally DEMOTES the previously active one rather than failing. Returns the created milestone (\xA77).",
     inputSchema: {
       project: projectKeySchema,
@@ -17045,7 +17017,7 @@ Every loose end has one destination, and none of them is prose. Anything you not
       active: external_exports.boolean().optional()
     }
   }, ({ project, ...input }) => run(() => client2.createMilestone(project, input)));
-  registerTool("update_milestone", {
+  server2.registerTool("update_milestone", {
     description: "Rename or reorder a milestone, addressed by its token (e.g. `M1`) or uuid. Supply at least one of `token`, `label`, or `position` \u2014 an empty edit is rejected. Renaming the `token` does NOT rewrite issues pointing at the old one (`issues.milestone` is a loose ref), so prefer changing `label`. Use set_active_milestone to change `active` (\xA77).",
     inputSchema: {
       project: projectKeySchema,
@@ -17055,14 +17027,14 @@ Every loose end has one destination, and none of them is prose. Anything you not
       position: external_exports.number().int().nonnegative().optional()
     }
   }, ({ project, milestone, ...fields }) => run(async () => client2.updateMilestone(project, await resolveMilestoneId(client2, project, milestone), fields)));
-  registerTool("set_active_milestone", {
+  server2.registerTool("set_active_milestone", {
     description: "Make a milestone the project\u2019s active one, addressed by its token (e.g. `M2`) or uuid. At most one milestone per project is active; this clears the previous one in the same transaction. Returns the activated milestone (\xA77).",
     inputSchema: {
       project: projectKeySchema,
       milestone: external_exports.string().min(1)
     }
   }, ({ project, milestone }) => run(async () => client2.activateMilestone(project, await resolveMilestoneId(client2, project, milestone))));
-  registerTool("delete_milestone", {
+  server2.registerTool("delete_milestone", {
     description: "Soft-delete a milestone, addressed by its token (e.g. `M3`) or uuid; its token frees up for reuse. Issues still naming it are NOT rewritten and keep the now-dangling token (`issues.milestone` is a loose ref) \u2014 re-point them first. Returns confirmation metadata only (\xA77).",
     inputSchema: {
       project: projectKeySchema,
@@ -17073,7 +17045,7 @@ Every loose end has one destination, and none of them is prose. Anything you not
     await client2.deleteMilestone(project, id);
     return { deleted: true, project, milestone, id };
   }));
-  registerTool("create_deliverable_target", {
+  server2.registerTool("create_deliverable_target", {
     description: "Add a deliverable target (platform) to a project. `slug` is the immutable lowercase-alphanumeric machine id a deliverable stores as its platform (e.g. `bsky`, `threads`) and is unique per project; `label` is its display name (e.g. `Bluesky`). Optional `position` orders it (0-based, defaults to last); optional `active` (default true) gates whether new deliverables can target it. Returns the created target.",
     inputSchema: {
       project: projectKeySchema,
@@ -17083,7 +17055,7 @@ Every loose end has one destination, and none of them is prose. Anything you not
       active: external_exports.boolean().optional()
     }
   }, ({ project, ...input }) => run(() => client2.createDeliverableTarget(project, input)));
-  registerTool("update_deliverable_target", {
+  server2.registerTool("update_deliverable_target", {
     description: "Update a deliverable target, addressed by its slug (e.g. `bsky`) or uuid. Supply at least one of `label`, `position`, or `active` \u2014 an empty edit is rejected. The `slug` is immutable (it is the value stored on existing deliverables). Set `active: false` to remove it from the add-deliverable menu while keeping existing deliverables working.",
     inputSchema: {
       project: projectKeySchema,
@@ -17093,7 +17065,7 @@ Every loose end has one destination, and none of them is prose. Anything you not
       active: external_exports.boolean().optional()
     }
   }, ({ project, target, ...fields }) => run(async () => client2.updateDeliverableTarget(project, await resolveDeliverableTargetId(client2, project, target), fields)));
-  registerTool("delete_deliverable_target", {
+  server2.registerTool("delete_deliverable_target", {
     description: "Delete a deliverable target, addressed by its slug (e.g. `bsky`) or uuid. Only a target with NO deliverables can be deleted; one already in use is rejected (deactivate it with update_deliverable_target instead). Returns confirmation metadata only.",
     inputSchema: {
       project: projectKeySchema,
@@ -17104,7 +17076,7 @@ Every loose end has one destination, and none of them is prose. Anything you not
     await client2.deleteDeliverableTarget(project, id);
     return { deleted: true, project, target, id };
   }));
-  registerTool(
+  server2.registerTool(
     "list_issues",
     {
       description: `List issue summaries (display id, title, type, status, terminal, blocked, priority, milestone, claimer, criteria progress, updated_at) filtered by project, environment, status[], type[], claimedBy (me/unclaimed/uuid), priority[], milestone, text (title+body), parent, and blocked (\xA77). DEFAULT: with no status filter this returns BUILDABLE work only \u2014 ${OPEN_STATUSES.join(", ")}. Terminal work (done, killed) is excluded unless you ask for it by name: pass status explicitly, e.g. status: ["done","killed"] for finished and abandoned work, or list every value to see everything. An explicit status filter is used verbatim and the default is not merged into it. Every row also carries \`terminal\` (PIPE-R15 r4 rule 5). blocked: false returns only work with nothing blocking it, and every issue it returns can be moved to ready without refusal; blocked: true returns only blocked work.`,
@@ -17120,78 +17092,83 @@ Every loose end has one destination, and none of them is prose. Anything you not
     // all, passes through untouched.
     (args) => run(() => client2.listIssues(args.status === void 0 ? { ...args, status: [...OPEN_STATUSES] } : args))
   );
-  registerTool("get_issue", {
-    description: "Full issue detail by display id or uuid: body, criteria (states, modes, evidence), explicit requirement links (pinned revision + staleness), the project\u2019s cross-cutting requirements at their latest approved revision, children, and comments (\xA77). Carries `terminal`: true when the issue is finished (`done`) or deliberately abandoned (`killed`) and is therefore NOT buildable work \u2014 check it before acting on an issue you were handed by key. Cross-cutting requirements bind every epic automatically and arrive with this payload at their latest approved revision \u2014 never restate them in a body; explicit requirement links pin the approved revision, so link by key rather than pasting a document\u2019s text. Reading criterion state: `state_evidence` is required only when a TOKEN sets one, so a `manual` criterion \u2014 settable only from a web session \u2014 carries none by design, and the attribution the server already stores (who set it, and when) IS its record. Absent evidence there is the human gate working rather than a gap: do not report it as a finding, do not call the criterion unverified or unevidenced, and do not weigh it below an `auto` criterion that carries evidence. What this payload tells you about ANOTHER issue goes stale. Reference that issue by key and say what you need from it; never restate its status, its criteria, or whether those criteria passed \u2014 such a sentence is true when written and wrong later, and a terminal issue is never revisited to correct it, so the stale reading is what the next reader inherits.",
+  server2.registerTool("get_issue", {
+    description: "Full issue detail by display id or uuid: body, criteria (states, modes, evidence), explicit requirement links (pinned revision + staleness), the project\u2019s cross-cutting requirements at their latest approved revision, children, and comments (\xA77). Carries `terminal`: true when the issue is finished (`done`) or deliberately abandoned (`killed`) and is therefore NOT buildable work \u2014 check it before acting on an issue you were handed by key. Reading criterion state: `state_evidence` is required only when a TOKEN sets one, so a `manual` criterion \u2014 settable only from a web session \u2014 carries none by design, and the attribution the server already stores (who set it, and when) IS its record. What this payload tells you about ANOTHER issue goes stale. Reference that issue by key and say what you need from it; never restate its status, its criteria, or whether those criteria passed \u2014 such a sentence is true when written and wrong later, and a terminal issue is never revisited to correct it, so the stale reading is what the next reader inherits.",
     inputSchema: { issue: issueRefSchema }
   }, (args) => run(() => client2.getIssue(args.issue)));
-  registerTool("create_issue", {
-    description: 'Create an issue (epic/task/bug/feedback). Omitted status defaults to triage (still subject to \xA76 guards); omitted environment resolves explicit \u2192 parent\u2019s environment \u2192 project default (prod). Optional parent (self/cycle rejected), priority, milestone, requirement_links (pins each at its approved revision; a target with no approved revision is rejected), deliverable_links (content deliverables like DWB-C3/bsky \u2014 pins each at its current revision; the promotion path), and ordered {text, verification, howTo} criteria (\xA77). A `status` other than `triage` or `killed` REQUIRES `milestone` (PIPE-R10 rule 9): work past triage belongs to a release, and the create is refused (`milestone_required`) without one. Search before you create: `list_issues` takes a `text` filter \u2014 run it on the distinctive nouns first. Sessions do not see each other, so a duplicate is invisible until someone finds both; on a near match, comment or amend the existing record rather than filing again. The bar for filing a bug: file `type: bug` only when the observed behavior breaks an approved requirement or a defined acceptance criterion, and name which one before you file. If you cannot name one, this is not a bug \u2014 code you find unclear, an edge case nobody specified, a performance number nobody set, and anything you would phrase as "this could be better" are opinions about the product, so file each as `type: feedback`, or not at all. The bar exists because a queue holding both real defects and unshared taste has to be read entirely before any of it can be trusted. When the criterion you named is an acceptance criterion, pass its uuid as `criterionId` and the bug records which criterion it was filed against \u2014 the criterion then names what has already been reported (it arrives as `filedBugs` on every criteria read) beside the action that files again, so a duplicate is prevented by information rather than by removal. Filing a second bug against one criterion is a supported situation, not a mistake: one row can fail for two different reasons at once. Bugs only: any other type naming a criterion is refused (`criterion_requires_bug`). Link another record by key plus title on first mention; never paste its text into a body \u2014 the source changes, the copy does not, and a stale copy gets built. A decision you need from the operator is filed as a question via `ask_questions`, never written as an "Open questions" heading inside a body \u2014 a heading prompts nobody and records no answer, so a later session cannot tell whether the decision was made. Before assigning any verification mode, establish what this project can drive end to end \u2014 an end-to-end test harness and the command that runs it. A criterion is `auto` when an evaluator can drive the input and read the result against the running system, which includes behavior shown in the interface wherever such a harness exists; the mode follows from what can be driven, not from where the behavior appears. What qualifies a criterion as `auto` is the evaluator\u2019s own run, never the existence of a test the implementer wrote. Mark `manual` only when the verdict needs a person\u2019s judgment; a criterion you cannot describe as drivable is usually worded too vaguely, so reword it against the observable rather than fall back to a person. A `manual` criterion must also carry `howTo` \u2014 one or two sentences, not an essay, saying where to look, what to do, and what counts as passing for whoever checks it by hand. Writing or changing one without it is refused (`how_to_required`); 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 \u2014 because what they answer is how anyone knows the thing is done, and that question does not get easier as the work gets smaller; feedback is the one exception, refused with `criteria_not_supported`, because it is a report rather than agreed work and `promote_feedback` retypes it into work before anything is built. Cross-cutting requirements bind every epic automatically and arrive with `get_issue` \u2014 never restate them in a body and never add them to `requirement_links`; an explicit link pins the linked document\u2019s approved revision.',
+  server2.registerTool("create_issue", {
+    description: "Create an issue (epic/task/bug/feedback). Omitted status defaults to triage (still subject to \xA76 guards); omitted environment resolves explicit \u2192 parent\u2019s environment \u2192 project default (prod). Optional parent (self/cycle rejected), priority, milestone, requirement_links (pins each at its approved revision; a target with no approved revision is rejected), deliverable_links (content deliverables like DWB-C3/bsky \u2014 pins each at its current revision; the promotion path), and ordered {text, verification, howTo} criteria (\xA77). A `status` other than `triage` or `killed` REQUIRES `milestone` (PIPE-R10 rule 9): work past triage belongs to a release, and the create is refused (`milestone_required`) without one. 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; `promote_feedback` retypes it into work before anything is built. When a bug is filed against a defined acceptance criterion, pass that criterion\u2019s uuid as `criterionId` and the bug records which criterion it was filed against \u2014 the criterion then names what has already been reported (it arrives as `filedBugs` on every criteria read) beside the action that files again, so a duplicate is prevented by information rather than by removal. Filing a second bug against one criterion is a supported situation, not a mistake: one row can fail for two different reasons at once. Bugs only: any other type naming a criterion is refused (`criterion_requires_bug`). Writing guidance for this tool lives in the product doctrine delivered at the start of this session \u2014 see \u201CSearch before you create\u201D and \u201CThe bar for filing a bug\u201D.",
     inputSchema: createIssueInputSchema.shape
   }, (args) => run(() => client2.createIssue(args)));
-  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, do not paste the feedback in. 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. Search before you promote: `list_issues` takes a `text` filter \u2014 run it on the feedback\u2019s distinctive nouns first; an issue covering it may already exist, and sessions do not see each other. On a near match, comment on or amend the existing issue rather than promoting a duplicate. The bar for promoting to a bug: choose `type: bug` only when the reported behavior breaks an approved requirement or a defined acceptance criterion, and name which one. If you cannot name one, promote it as `task` \u2014 or leave it as feedback. A queue holding both real defects and unshared taste has to be read entirely before any of it can be trusted. Link another record by key plus title on first mention; never paste its text into a body \u2014 the source changes, the copy does not, and a stale copy gets built. A decision you need from the operator is filed as a question via `ask_questions`, never written as an "Open questions" heading inside a body \u2014 a heading prompts nobody and records no answer, so a later session cannot tell whether the decision was made. Before assigning any verification mode, establish what this project can drive end to end \u2014 an end-to-end test harness and the command that runs it. A criterion is `auto` when an evaluator can drive the input and read the result against the running system, which includes behavior shown in the interface wherever such a harness exists; the mode follows from what can be driven, not from where the behavior appears. What qualifies a criterion as `auto` is the evaluator\u2019s own run, never the existence of a test the implementer wrote. Mark `manual` only when the verdict needs a person\u2019s judgment; a criterion you cannot describe as drivable is usually worded too vaguely, so reword it against the observable rather than fall back to a person. A `manual` criterion must also carry `howTo` \u2014 one or two sentences, not an essay, saying where to look, what to do, and what counts as passing for whoever checks it by hand. Writing or changing one without it is refused (`how_to_required`); 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 \u2014 because what they answer is how anyone knows the thing is done, and that question does not get easier as the work gets smaller; feedback is the one exception, refused with `criteria_not_supported`, because it is a report rather than agreed work and `promote_feedback` retypes it into work before anything is built. Cross-cutting requirements bind every epic automatically and arrive with `get_issue` \u2014 never restate them in a body and never add them to `requirement_links`; an explicit link pins the linked document\u2019s approved revision.',
+  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 delivered at the start of this session \u2014 see \u201CSearch before you create\u201D and \u201CThe bar for filing a bug\u201D.",
     inputSchema: {
       issue: external_exports.string().min(1),
       ...promoteFeedbackInputSchema.shape
     }
   }, ({ issue: issue2, ...fields }) => run(() => client2.promoteFeedback(issue2, fields)));
-  registerTool("open_review", {
-    description: "Open the COMPLETION REVIEW \u2014 the reading of an epic\u2019s WHOLE accumulated change as one body of work, by a third fresh session that neither built it nor evaluated it. It runs at one moment: once the epic\u2019s contract is green and nothing is left to check, and before anyone sets it `done`. It creates one ORDINARY `task` at `ready` carrying the review checklist as its body \u2014 no new record type. The epic form (`epic`) titles it `Completion review \u2014 <KEY-n> <epic title>`, files it as a CHILD of the epic and inherits the epic\u2019s milestone; the milestone form (`project` + `milestone`) titles it `Completion review \u2014 milestone <token>`, carries that token and has no parent \u2014 nothing here models a milestone as complete. Pass EXACTLY ONE of `epic` or `project` + `milestone`: both, or neither, is refused. One review at a time per scope \u2014 a second is refused (`review_already_open`) NAMING the standing one, so read, finish or kill that task instead \u2014 and a review opens only on an epic (`review_target_not_epic`). NO NEW GATE was added to `done`, and the whole mechanism depends on that: file each finding as ordinary work \u2014 a CHILD OF THE EPIC, a sibling of this review \u2014 and the children clause already on `done` holds the epic open until every finding is done or killed. A finding filed UNDER the review gates nothing, because that gate reads one level deep. Killing the review, or any finding, is the recorded waiver: deliberately ungated, and written to the status history with who did it and through which token. An epic that never opened a review still closes exactly as it did before.",
+  server2.registerTool("open_review", {
+    description: "Open the COMPLETION REVIEW \u2014 the reading of an epic\u2019s WHOLE accumulated change as one body of work, by a third fresh session that neither built it nor evaluated it. It runs at one moment: once the epic\u2019s contract is green and nothing is left to check, and before anyone sets it `done`. It creates one ORDINARY `task` at `ready` carrying the review checklist as its body \u2014 no new record type. The epic form (`epic`) titles it `Completion review \u2014 <KEY-n> <epic title>`, files it as a CHILD of the epic and inherits the epic\u2019s milestone; the milestone form (`project` + `milestone`) titles it `Completion review \u2014 milestone <token>`, carries that token and has no parent \u2014 nothing here models a milestone as complete. Pass EXACTLY ONE of `epic` or `project` + `milestone`: both, or neither, is refused. One review at a time per scope \u2014 a second is refused (`review_already_open`) NAMING the standing one, so read, finish or kill that task instead \u2014 and a review opens only on an epic (`review_target_not_epic`). NO NEW GATE was added to `done`, and the whole mechanism depends on that: file each finding as ordinary work \u2014 a CHILD OF THE EPIC, a sibling of this review \u2014 and the children clause already on `done` holds the epic open until every finding is done or killed. A finding filed UNDER the review gates nothing, because that gate reads one level deep. Killing the review, or any finding, is the recorded waiver: deliberately ungated, and written to the status history with who did it and through which token. An epic that never opened a review still closes exactly as it did before. Writing guidance for the checklist and for each finding lives in the product doctrine delivered at the start of this session.",
     // The WHOLE domain schema rather than its `.shape`, for `get_work_context`'s
     // reason: the exactly-one-of rule is a refinement on the OBJECT, and a raw
     // shape drops it — the refusal naming the two forms would never reach the
     // caller, and both arguments (or neither) would be accepted here.
     inputSchema: openReviewInputSchema
   }, (args) => run(() => client2.openReview(args)));
-  registerTool("update_issue", {
-    description: 'Update any subset of an issue\u2019s title, body, type, priority, milestone, environment, parent (self/cycle rejected), requirement_links (add/remove; adding a link to an unapproved requirement is rejected), deliverable_links (add/remove content-deliverable links, add pins at the current revision), or decision_links (add/remove decision records this work sits under \u2014 `KEY-D{n}`, from `list_decisions`). Changing type to `feedback` is rejected while the issue has criteria (\xA77), since feedback carries none; epic, task and bug interchange freely and the criteria ride along, keeping their AC-{n} numbers and their states. Clearing `milestone` (passing null) is rejected while the issue sits past `triage` \u2014 work already scheduled keeps a milestone (PIPE-R10 rule 9); swap it for a different one, or move the issue back to `triage` first. Cite the decision record a piece of work implements rather than restating what was decided in its body: the record is where the reasoning stays correct, and a body repeating it goes stale the moment the decision is superseded. Link another record by key plus title on first mention; never paste its text into a body \u2014 the source changes, the copy does not, and a stale copy gets built. A decision you need from the operator is filed as a question via `ask_questions`, never written as an "Open questions" heading inside a body \u2014 a heading prompts nobody and records no answer, so a later session cannot tell whether the decision was made. Cross-cutting requirements bind every epic automatically and arrive with `get_issue` \u2014 never restate them in a body and never add them to `requirement_links`; an explicit link pins the linked document\u2019s approved revision.',
+  server2.registerTool("update_issue", {
+    description: "Update any subset of an issue\u2019s title, body, type, priority, milestone, environment, parent (self/cycle rejected), requirement_links (add/remove; adding a link to an unapproved requirement is rejected), deliverable_links (add/remove content-deliverable links, add pins at the current revision), or decision_links (add/remove decision records this work sits under \u2014 `KEY-D{n}`, from `list_decisions`). Changing type to `feedback` is rejected while the issue has criteria (\xA77), since feedback carries none; epic, task and bug interchange freely and the criteria ride along, keeping their AC-{n} numbers and their states. Clearing `milestone` (passing null) is rejected while the issue sits past `triage` \u2014 work already scheduled keeps a milestone (PIPE-R10 rule 9); swap it for a different one, or move the issue back to `triage` first. Writing guidance for this tool lives in the product doctrine delivered at the start of this session \u2014 see \u201CLink by key; never paste another record\u2019s text\u201D and \u201CA decision you need is filed as a question, never written into a body\u201D.",
     inputSchema: updateIssueInputSchema.shape
   }, ({ issue: issue2, ...fields }) => run(() => client2.updateIssue(issue2, fields)));
-  registerTool("set_status", {
+  server2.registerTool("set_status", {
     description: "Set an issue\u2019s status; the \xA76 guards apply and a guard failure returns the specific reason, naming the rows it refused on (\xA77). The criteria gates read whatever criteria the issue carries, whatever its type: verify needs every auto criterion passed, done needs every criterion passed. ONE guard remains EPIC-ONLY, and the asymmetry is the rule rather than an oversight \u2014 an epic that has stated NO criteria is refused at both gates, because an empty list would clear them having committed to nothing, while a task or a bug carrying none moves through both untouched (most work is stated adequately by its body). `done` additionally requires every child of the issue being closed to be terminal \u2014 an epic, a task and a bug alike \u2014 read from each child\u2019s STATUS and never from its criteria. A BLOCKED issue \u2014 one carrying an explicit mark or waiting on a blocker that is not yet `done`/`killed` \u2014 cannot move to `ready` or `in_progress`, and the refusal names the reason and every unresolved blocker, so clear the mark (`clear_blocked`) or finish, kill or `unlink_blocker` each blocker first; every other target still moves while blocked. An issue with NO milestone cannot move to any status but `triage` and `killed` (PIPE-R10 rule 9) \u2014 set one with `update_issue` first; `killed` is exempt, so work nobody scheduled can still be abandoned.",
     inputSchema: setStatusInputSchema.shape
   }, (args) => run(() => client2.setStatus(args.issue, args.status)));
-  registerTool("claim_issue", {
+  server2.registerTool("claim_issue", {
     description: "Atomically claim an issue (\xA76 rule 1): succeeds only if unclaimed; under a race exactly one wins and the loser\u2019s error names the current claimer. Claim is orthogonal to status (\xA77).",
     inputSchema: { issue: issueRefSchema }
   }, (args) => run(() => client2.claimIssue(args.issue)));
-  registerTool("release_issue", {
+  server2.registerTool("release_issue", {
     description: "Release an issue\u2019s claim, clearing claimed_by (\xA77).",
     inputSchema: { issue: issueRefSchema }
   }, (args) => run(() => client2.releaseIssue(args.issue)));
-  registerTool("add_comment", {
-    description: "Add a markdown comment to an issue, attributed to the operator (and token label over MCP). A comment EXPLAINS a blockage \u2014 the full account of what you hit and why you stopped \u2014 but never records one: `set_blocked` (with a reason) and `link_blocker` (when you are waiting on another issue) are what put an issue in the blocked state (\xA77/WORKFLOW).",
+  server2.registerTool("add_comment", {
+    description: "Add a markdown comment to an issue, attributed to the operator (and token label over MCP). A comment EXPLAINS a blockage \u2014 the full account of what you hit and why you stopped \u2014 but never records one: `set_blocked` (with a reason) and `link_blocker` (when you are waiting on another issue) are what put an issue in the blocked state (\xA77/WORKFLOW). Writing guidance for a comment lives in the product doctrine delivered at the start of this session \u2014 see \u201CEvery loose end has one destination, and none of them is prose\u201D.",
     inputSchema: commentInputSchema.shape
   }, (args) => run(() => client2.addComment(args.issue, args.body)));
-  registerTool("set_blocked", {
-    description: "Record an issue as BLOCKED with a required human-readable `reason` \u2014 state on the issue, not a comment: it shows on the issue and counts on the project\u2019s Work page, and only clearing it (`clear_blocked`) ends it. Setting it again on an already-blocked issue replaces the standing reason and keeps the old one as history, attributed to whoever set it. The reason is one or two lines saying what the work is waiting on; the full account of what you tried still belongs in a comment. Returns the updated issue detail, whose `blocked` carries the reason and who set it.",
+  server2.registerTool("set_blocked", {
+    description: "Record an issue as BLOCKED with a required human-readable `reason` \u2014 state on the issue, not a comment: it shows on the issue and counts on the project\u2019s Work page, and only clearing it (`clear_blocked`) ends it. Setting it again on an already-blocked issue replaces the standing reason and keeps the old one as history, attributed to whoever set it. The reason is one or two lines saying what the work is waiting on; the full account of what you tried still belongs in a comment. Returns the updated issue detail, whose `blocked` carries the reason and who set it. Writing guidance for the reason lives in the product doctrine delivered at the start of this session.",
     inputSchema: setBlockedInputSchema.shape
   }, (args) => run(() => client2.setBlocked(args.issue, args.reason)));
-  registerTool("clear_blocked", {
+  server2.registerTool("clear_blocked", {
     description: "Clear an issue\u2019s blocked mark \u2014 the blockage is over. Idempotent: clearing an issue that is not blocked is a no-op, not an error. The cleared mark is kept as history with who ended it, so a past blockage stays readable. Returns the updated issue detail (`blocked` is then null).",
     inputSchema: { issue: issueRefSchema }
   }, (args) => run(() => client2.clearBlocked(args.issue)));
-  registerTool("link_blocker", {
+  server2.registerTool("link_blocker", {
     description: "Record that `issue` is WAITING ON `blocker` \u2014 the dependency between two issues, written from the waiting issue\u2019s side. One call records both directions: `get_issue` on the waiting issue lists it under `blockedBy` (with the blocker\u2019s display id, title, and whether it is already `done`/`killed`), and `get_issue` on the blocker lists it under `blocks`, so finishing work shows what it frees. Both issues must be in the SAME project. An issue cannot block itself, and an edge that would close a cycle (directly or through other issues) is refused with nothing recorded. Adding the same blocker twice records no second edge. Returns the waiting issue\u2019s updated detail.",
     inputSchema: linkBlockerInputSchema.shape
   }, (args) => run(() => client2.addBlocker(args.issue, args.blocker)));
-  registerTool("unlink_blocker", {
+  server2.registerTool("unlink_blocker", {
     description: "Remove the blocked-by edge between `issue` and `blocker` \u2014 the dependency is gone, and one call clears it from BOTH issues\u2019 views. Idempotent: unlinking a pair that is not linked is a no-op, not an error. Returns the waiting issue\u2019s updated detail.",
     inputSchema: linkBlockerInputSchema.shape
   }, (args) => run(() => client2.removeBlocker(args.issue, args.blocker)));
-  registerTool("set_criteria", {
-    description: "Define or replace the ordered acceptance criteria list ({text, verification, howTo}) on a piece of work. Matched rows keep their stable AC-{n} number; new items get fresh never-reused numbers; removed items are soft-deleted. A matched row keeps its state only when BOTH its text and verification mode are unchanged \u2014 a mode flip resets it to pending (\xA77). Before assigning any verification mode, establish what this project can drive end to end \u2014 an end-to-end test harness and the command that runs it. A criterion is `auto` when an evaluator can drive the input and read the result against the running system, which includes behavior shown in the interface wherever such a harness exists; the mode follows from what can be driven, not from where the behavior appears. What qualifies a criterion as `auto` is the evaluator\u2019s own run, never the existence of a test the implementer wrote. Mark `manual` only when the verdict needs a person\u2019s judgment; a criterion you cannot describe as drivable is usually worded too vaguely, so reword it against the observable rather than fall back to a person. A `manual` criterion must also carry `howTo` \u2014 one or two sentences, not an essay, saying where to look, what to do, and what counts as passing for whoever checks it by hand. Writing or changing one without it is refused (`how_to_required`); 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 \u2014 because what they answer is how anyone knows the thing is done, and that question does not get easier as the work gets smaller; feedback is the one exception, refused with `criteria_not_supported`, because it is a report rather than agreed work and `promote_feedback` retypes it into work before anything is built. An evaluator RAISES a criterion from `manual` to `auto` only on a drive that actually succeeded \u2014 never on one it expects to succeed \u2014 and never lowers one. The flip both resets the state and clears the stored `howTo`, so a criterion moved to `auto` has lost its checking instructions \u2014 moving it back to `manual` does not restore them, and is refused (`how_to_required`) until you write new ones.",
+  server2.registerTool("set_criteria", {
+    description: "Define or replace the ordered acceptance criteria list ({text, verification, howTo}) on a piece of work. Matched rows keep their stable AC-{n} number; new items get fresh never-reused numbers; removed items are soft-deleted. A matched row keeps its state only when BOTH its text and verification mode are unchanged \u2014 a mode flip resets it to pending (\xA77). 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; `promote_feedback` retypes it into work before anything is built. Raising a criterion from `manual` to `auto` both resets its state and clears the stored `howTo`, so a criterion moved to `auto` has lost its checking instructions \u2014 moving it back to `manual` does not restore them, and is refused (`how_to_required`) until you write new ones. Writing guidance for a criterion, and for choosing its mode, lives in the product doctrine delivered at the start of this session \u2014 see \u201CVerification modes follow what can be driven\u201D.",
     inputSchema: setCriteriaInputSchema.shape
   }, (args) => run(() => client2.setCriteria(args.issue, args.criteria)));
-  registerTool("set_criterion_state", {
-    description: "Set a criterion\u2019s state (pending/passed/failed) on whatever work carries it \u2014 an epic, a task and a bug alike \u2014 addressed by criterionId ALONE, or by issue + criterionNumber (the stable AC-{n}); exactly one form. Feedback never carries criteria, so neither address resolves to one. A token-authenticated call is REJECTED on a manual criterion (manual state is web-session-only, \xA74); evidence is required when a token marks passed/failed (\xA77).",
+  server2.registerTool("set_criterion_state", {
+    description: "Set a criterion\u2019s state (pending/passed/failed) on whatever work carries it \u2014 an epic, a task and a bug alike \u2014 addressed by criterionId ALONE, or by issue + criterionNumber (the stable AC-{n}); exactly one form. Feedback never carries criteria, so neither address resolves to one. A token-authenticated call is REJECTED on a manual criterion (manual state is web-session-only, \xA74); evidence is required when a token marks passed/failed (\xA77). Writing guidance for that evidence lives in the product doctrine delivered at the start of this session \u2014 see \u201CVerification modes follow what can be driven\u201D.",
     // `issue` is OPTIONAL: the criterionId-only form needs no issue ref. The
     // exactly-one-of rule can't be expressed in a raw shape, so the handler
     // enforces it via the shared `@pipeline/domain` refine (mirror of §7).
+    //
+    // `criterionNumber` takes `int4Schema` so the ADVERTISED JSON Schema carries
+    // the real ceiling (PIPE-149) — hand-rolling it from `positiveIntSchema` told
+    // clients the maximum was 2^53-1 while the column and the API both stop at
+    // 2,147,483,647, so a client refusal that should happen never did.
     inputSchema: {
       issue: issueRefSchema.optional(),
       criterionId: uuidSchema.optional(),
-      criterionNumber: positiveIntSchema.optional(),
+      criterionNumber: int4Schema.optional(),
       state: criterionStateSchema,
       evidence: markdownSchema.optional()
     }
@@ -17209,28 +17186,28 @@ Every loose end has one destination, and none of them is prose. Anything you not
       evidence: input.evidence
     });
   }));
-  registerTool("ask_questions", {
-    description: 'Ask the operator a BATCH of questions on an issue \u2014 `questions` takes 1 or more {text, options?}, and a session with one open decision usually has two or three, so ask them in ONE call rather than one at a time (a half-asked set costs the operator a second pass). `options` are the choices you propose, in the order you offer them; omit it to ask in open words. Each question gets a stable per-issue `Q-{n}` number that is NEVER reused, so an answer stays addressable in a later session. Returns the updated issue detail, and every issue read from then on carries `questions` with their answers \u2014 so read the answer in the `get_issue` you were going to make anyway, and READ the existing questions and answers BEFORE asking again rather than re-asking a decision already taken. Answering is reserved for a person in the web UI: there is deliberately no tool for it on this surface (PIPE-R22 rule 4). A decision you need from the operator is filed HERE, never written as an "Open questions" heading inside an issue body \u2014 a heading prompts nobody and records no answer, so a later session cannot tell whether the decision was made. Withdraw any question your own work has since settled, with `withdraw_question` \u2014 an open question the work already answered still asks the operator to decide something nobody is waiting on.',
+  server2.registerTool("ask_questions", {
+    description: "Ask the operator a BATCH of questions on an issue \u2014 `questions` takes 1 or more {text, options?}, and a session with one open decision usually has two or three, so ask them in ONE call rather than one at a time (a half-asked set costs the operator a second pass). `options` are the choices you propose, in the order you offer them; omit it to ask in open words. Each question gets a stable per-issue `Q-{n}` number that is NEVER reused. Returns the updated issue detail, and every issue read from then on carries `questions` with their answers \u2014 so read the answer in the `get_issue` you were going to make anyway, and READ the existing questions and answers BEFORE asking again rather than re-asking a decision already taken. Answering is reserved for a person in the web UI: there is deliberately no tool for it on this surface (PIPE-R22 rule 4). A question is withdrawn with `withdraw_question`. Writing guidance for a question lives in the product doctrine delivered at the start of this session \u2014 see \u201CA decision you need is filed as a question, never written into a body\u201D.",
     inputSchema: askQuestionsInputSchema.shape
   }, (args) => run(() => client2.askQuestions(args.issue, args.questions)));
-  registerTool("withdraw_question", {
+  server2.registerTool("withdraw_question", {
     description: "Withdraw a question by its stable `Q-{n}` number \u2014 asker only: the asker is the token\u2019s OWNING user, so another agent\u2019s question is not yours to clear. Deliberately NOT human-gated, because the point is to clear a question you no longer need \u2014 the work answered it, or it was wrong to ask \u2014 instead of leaving the operator to answer something nobody is waiting on. It is recorded, never an answer: the question is soft-deleted (kept for the audit trail), its number retires and is not reissued, and the next issue read no longer carries it in `questions`. Returns the updated issue detail.",
     inputSchema: withdrawQuestionInputSchema.shape
   }, (args) => run(() => client2.withdrawQuestion(args.issue, args.number)));
-  registerTool("list_requirements", {
+  server2.registerTool("list_requirements", {
     description: "List requirements filtered by project and text: display id, title, summary (the latest revision\u2019s one/two-line outline description), area (product-area label), cross_cutting flag, lifecycle (draft/approved/amended), latest + approved revision numbers, and linked-epic count (\xA77).",
     inputSchema: listRequirementsFilterSchema.shape
   }, (args) => run(() => client2.listRequirements(args)));
-  registerTool("get_requirement", {
+  server2.registerTool("get_requirement", {
     description: "Get a requirement by display id or uuid. Defaults to the approved revision (latest if never approved) unless `revision` is given; includes lifecycle, revision list, approvals, and linked issues (\xA77).",
     inputSchema: { requirement: requirementRefSchema, revision: positiveIntSchema.optional() }
   }, (args) => run(() => client2.getRequirement(args.requirement, args.revision)));
-  registerTool("create_requirement", {
-    description: 'Create a project-scoped requirement document with revision 1 (title, body). Optional summary is a short one/two-line outline description (versioned on the revision, like title/body); optional area is a free-text product-area label ("Backup", "Billing") used to group/filter the outline (metadata, like cross_cutting). Optional cross_cutting flags it as binding every epic in the project automatically \u2014 never link cross-cutting documents (\xA75 rule 6, \xA77). Search before you create: `list_requirements` takes a `text` filter \u2014 run it on the distinctive nouns first. Sessions do not see each other, so a duplicate is invisible until someone finds both; on a near match, amend the existing document rather than filing again. Link another record by key plus title on first mention; never paste its text into a body \u2014 the source changes, the copy does not, and a stale copy gets built.',
+  server2.registerTool("create_requirement", {
+    description: 'Create a project-scoped requirement document with revision 1 (title, body). Optional summary is a short one/two-line outline description (versioned on the revision, like title/body); optional area is a free-text product-area label ("Backup", "Billing") used to group/filter the outline (metadata, like cross_cutting). Optional cross_cutting flags it as binding every epic in the project automatically \u2014 never link cross-cutting documents (\xA75 rule 6, \xA77). Writing guidance for this tool lives in the product doctrine delivered at the start of this session \u2014 see \u201CSearch before you create\u201D and \u201CLink by key; never paste another record\u2019s text\u201D.',
     inputSchema: createRequirementInputSchema.shape
   }, (args) => run(() => client2.createRequirement(args)));
-  registerTool("update_requirement", {
-    description: "Update a requirement: title, body, and/or summary APPENDS a new revision (nothing is edited in place; summary versions like title/body); optional note records why. Optional area (product-area label), cross_cutting, and decision_links (add/remove decision records this rule sits under \u2014 `KEY-D{n}`, from `list_decisions`) are metadata changes (no revision) \u2014 toggling cross_cutting ON is rejected while explicit links exist; unlink first. Supplying none of title/body/summary/area/cross_cutting/decision_links is an empty edit (400) (\xA77). Cite the decision record a rule rests on rather than restating what was decided in its body: the record is where the reasoning stays correct, and a body repeating it goes stale the moment the decision is superseded. Link another record by key plus title on first mention; never paste its text into a body \u2014 the source changes, the copy does not, and a stale copy gets built.",
+  server2.registerTool("update_requirement", {
+    description: "Update a requirement: title, body, and/or summary APPENDS a new revision (nothing is edited in place; summary versions like title/body); optional note records why. Optional area (product-area label), cross_cutting, and decision_links (add/remove decision records this rule sits under \u2014 `KEY-D{n}`, from `list_decisions`) are metadata changes (no revision) \u2014 toggling cross_cutting ON is rejected while explicit links exist; unlink first. Supplying none of title/body/summary/area/cross_cutting/decision_links is an empty edit (400) (\xA77). Writing guidance for this tool lives in the product doctrine delivered at the start of this session \u2014 see \u201CLink by key; never paste another record\u2019s text\u201D.",
     // Inline shape (updateRequirementInputSchema is a refine, no .shape) — add
     // summary/area here explicitly (§210) and decisionLinks (PIPE-84 §6); the
     // empty-edit refine is enforced by the API, not this shape.
@@ -17245,56 +17222,56 @@ Every loose end has one destination, and none of them is prose. Anything you not
       decisionLinks: decisionLinkChangesSchema.optional()
     }
   }, ({ requirement, ...fields }) => run(() => client2.updateRequirement(requirement, fields)));
-  registerTool("approve_requirement", {
+  server2.registerTool("approve_requirement", {
     description: "Approve (pin) a requirement\u2019s latest revision, or a specified `revision`, recording it in approvals history and advancing the approved revision that downstream links and reads build against (\xA75, \xA77).",
     inputSchema: approveRequirementInputSchema.shape
   }, (args) => run(() => client2.approveRequirement(args.requirement, args.revision)));
-  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. A decision record is written ONCE. Title and body can be corrected only while it is `proposed`; from `accepted` onward the record 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. Search before you create: `list_decisions` takes a `text` filter matching TITLE AND BODY \u2014 run it on the distinctive nouns first. Sessions do not see each other, so re-arguing a settled question leaves two answers on the ledger with nothing saying which one holds. Link another record by key plus title on first mention; never paste its text into a body \u2014 the source changes, the copy does not, and a stale copy gets built.",
+  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 delivered at the start of this session \u2014 see \u201CA decision record is written once\u201D and \u201CSearch before you create\u201D.",
     inputSchema: createDecisionInputSchema.shape
   }, (args) => run(() => client2.createDecision(args)));
-  registerTool("get_decision", {
+  server2.registerTool("get_decision", {
     description: "Get a decision record by display id (`KEY-D{n}`) or uuid: title, body, lifecycle state (`proposed`/`accepted`/`superseded`), who accepted it and when, the record that replaced it, where the CURRENT decision lives when this one has been superseded, and everything that references it \u2014 every requirement and every work item, gathered from both directions.",
     inputSchema: getDecisionInputSchema.shape
   }, (args) => run(() => client2.getDecision(args.decision)));
-  registerTool("list_decisions", {
-    description: "List decision records filtered by `project` and `text`: display id, title, lifecycle state, the replacement when superseded, and how many requirements and work items cite each one. `text` matches over TITLE AND BODY, so search on what a decision was about rather than on what someone chose to call it. Read the decisions before re-opening a settled question: an `accepted` record is the project\u2019s answer, and arguing it again inside an issue or requirement body produces a second answer with nothing saying which one holds. If the answer genuinely has changed, record a NEW decision and `supersede_decision` the old one rather than editing anything.",
+  server2.registerTool("list_decisions", {
+    description: "List decision records filtered by `project` and `text`: display id, title, lifecycle state, the replacement when superseded, and how many requirements and work items cite each one. `text` matches over TITLE AND BODY, so search on what a decision was about rather than on what someone chose to call it.",
     inputSchema: listDecisionsFilterSchema.shape
   }, (args) => run(() => client2.listDecisions(args)));
-  registerTool("supersede_decision", {
+  server2.registerTool("supersede_decision", {
     description: "Replace an ACCEPTED decision record with another one: `decision` moves to `superseded` and names `replacedBy` as where the current decision now lives, so whoever opens the old record is sent to the standing one. This is the only way a decision changes \u2014 the original is never edited and never removed, and the whole chain stays readable. Refused when the record is still `proposed` (nothing has been decided yet, so correct it instead), when a record is named as its own replacement, when the replacement belongs to another project, or when the replacement\u2019s own chain already leads back to this record. Returns the superseded record.",
     inputSchema: supersedeDecisionInputSchema.shape
   }, (args) => run(() => client2.supersedeDecision(args.decision, args.replacedBy)));
-  registerTool("list_content", {
+  server2.registerTool("list_content", {
     description: "List content drafts filtered by project, text, area, and author: display id (KEY-C{n}), title, summary (latest revision), area, author, latest revision number, deliverable count, and linked-issue count. Content is a project-scoped sibling of requirements \u2014 raw material that gets promoted into work, not an issue type.",
     inputSchema: listContentFilterSchema.shape
   }, (args) => run(() => client2.listContent(args)));
-  registerTool("get_content", {
+  server2.registerTool("get_content", {
     description: "Get a content draft by display id (KEY-C{n}) or uuid: its revision history (default latest, or `revision` to pin) plus every per-platform deliverable with its own revisions, posted metadata (url/postedAt), linked issues (with staleness), and linked assets.",
     inputSchema: { content: contentRefSchema, revision: positiveIntSchema.optional() }
   }, (args) => run(() => client2.getContent(args.content, args.revision)));
-  registerTool("create_content", {
-    description: 'Create a project-scoped content draft with revision 1 (title, body). Optional summary is a short outline description (versioned on the revision, like title/body); optional area is a free-text product-area label (metadata). Optional author is the editorial byline the draft is credited to (free text, e.g. "jason") \u2014 distinct from the acting operator, and the field the list filters by. Optional metadata is an open bag for capture provenance (tags, score, sensitivity, source refs) \u2014 stored passively, never acted on. This is the capture-sink target: a captured topic becomes a draft here. Search before you create: `list_content` takes a `text` filter \u2014 run it on the distinctive nouns first. Sessions do not see each other, so a duplicate is invisible until someone finds both; on a near match, amend the existing draft rather than filing again.',
+  server2.registerTool("create_content", {
+    description: 'Create a project-scoped content draft with revision 1 (title, body). Optional summary is a short outline description (versioned on the revision, like title/body); optional area is a free-text product-area label (metadata). Optional author is the editorial byline the draft is credited to (free text, e.g. "jason") \u2014 distinct from the acting operator, and the field the list filters by. Optional metadata is an open bag for capture provenance (tags, score, sensitivity, source refs) \u2014 stored passively, never acted on. This is the capture-sink target: a captured topic becomes a draft here. Writing guidance for this tool lives in the product doctrine delivered at the start of this session \u2014 see \u201CSearch before you create\u201D.',
     inputSchema: createContentInputSchema.shape
   }, (args) => run(() => client2.createContent(args)));
-  registerTool("update_content", {
-    description: "Update a content draft: title, body, and/or summary APPENDS a new revision (nothing is edited in place); optional note records why. Optional area, author, and metadata are metadata changes (no revision). Supplying none of title/body/summary/area/author/metadata is an empty edit (400).",
+  server2.registerTool("update_content", {
+    description: "Update a content draft: title, body, and/or summary APPENDS a new revision (nothing is edited in place); optional note records why. Optional area, author, and metadata are metadata changes (no revision). Supplying none of title/body/summary/area/author/metadata is an empty edit (400). Writing guidance for this tool lives in the product doctrine delivered at the start of this session.",
     inputSchema: updateContentInputSchema.shape
   }, ({ content, ...fields }) => run(() => client2.updateContent(content, fields)));
-  registerTool("create_deliverable", {
-    description: "Add a per-platform deliverable to a draft with revision 1 (the post text). `platform` is a slug configured for the project \u2014 one of its ACTIVE deliverable targets (see list_projects \u2192 deliverableTargets; defaults are bsky/x/reddit/hn/blog, but projects can add/remove them); an unconfigured slug is rejected. Optional body seeds revision 1. There is one deliverable per platform per draft \u2014 a variant is a revision (update_deliverable), not a second deliverable. Rendered id is DRAFT-KEY/platform (e.g. DWB-C3/bsky).",
+  server2.registerTool("create_deliverable", {
+    description: "Add a per-platform deliverable to a draft with revision 1 (the post text). `platform` is a slug configured for the project \u2014 one of its ACTIVE deliverable targets (see list_projects \u2192 deliverableTargets; defaults are bsky/x/reddit/hn/blog, but projects can add/remove them); an unconfigured slug is rejected. Optional body seeds revision 1. There is one deliverable per platform per draft \u2014 a variant is a revision (update_deliverable), not a second deliverable. Rendered id is DRAFT-KEY/platform (e.g. DWB-C3/bsky). Writing guidance for the post text lives in the product doctrine delivered at the start of this session.",
     inputSchema: createDeliverableInputSchema.shape
   }, ({ content, ...fields }) => run(() => client2.createDeliverable(content, fields)));
-  registerTool("update_deliverable", {
-    description: "Append a new revision (post text) to a deliverable, addressed as DRAFT-KEY/platform (e.g. DWB-C3/bsky); optional note records why. Platform identity is immutable \u2014 this only versions the post text.",
+  server2.registerTool("update_deliverable", {
+    description: "Append a new revision (post text) to a deliverable, addressed as DRAFT-KEY/platform (e.g. DWB-C3/bsky); optional note records why. Platform identity is immutable \u2014 this only versions the post text. Writing guidance for the post text lives in the product doctrine delivered at the start of this session.",
     inputSchema: updateDeliverableInputSchema.shape
   }, ({ deliverable, ...fields }) => run(() => client2.updateDeliverable(deliverable, fields)));
-  registerTool("record_post", {
+  server2.registerTool("record_post", {
     description: "Record that a deliverable (DRAFT-KEY/platform) was posted: its public url and when (postedAt defaults to now), pinning the deliverable\u2019s current revision as the posted one. Pipebrain never posts \u2014 a human posts, then records the url here. Re-calling overwrites (a correction).",
     inputSchema: recordPostInputSchema.shape
   }, ({ deliverable, ...fields }) => run(() => client2.recordPost(deliverable, fields)));
-  registerTool("promote_deliverable", {
-    description: 'Promote a deliverable (DRAFT-KEY/platform, e.g. DWB-C3/bsky) to a NEW issue: creates the issue (`title` + `type` required; optional `status` defaults to triage; optional `body` seeds it \u2014 typically the current post text) AND a PROTECTED link pinning the deliverable\u2019s current revision. That link CANNOT be unlinked \u2014 the issue exists to ship this deliverable. (To link an EXISTING issue instead, use update_issue.deliverable_links, which stays removable.) Returns the created issue. Search before you promote: `list_issues` takes a `text` filter \u2014 run it on the deliverable\u2019s distinctive nouns first; an issue for this deliverable may already exist, and sessions do not see each other. Link another record by key plus title on first mention; never paste its text into a body \u2014 the source changes, the copy does not, and a stale copy gets built. The promoted deliverable itself is the exception: seeding the body with its text is the point of this tool, and the protected link pins the revision that text came from. A decision you need from the operator is filed as a question via `ask_questions`, never written as an "Open questions" heading inside a body \u2014 a heading prompts nobody and records no answer, so a later session cannot tell whether the decision was made.',
+  server2.registerTool("promote_deliverable", {
+    description: "Promote a deliverable (DRAFT-KEY/platform, e.g. DWB-C3/bsky) to a NEW issue: creates the issue (`title` + `type` required; optional `status` defaults to triage; optional `body` seeds it \u2014 typically the current post text) AND a PROTECTED link pinning the deliverable\u2019s current revision. That link CANNOT be unlinked \u2014 the issue exists to ship this deliverable. (To link an EXISTING issue instead, use update_issue.deliverable_links, which stays removable.) Returns the created issue. Seeding the body with the deliverable\u2019s own text is the exception to linking rather than pasting \u2014 it is the point of this tool, and the protected link pins the revision that text came from. Writing guidance for this tool lives in the product doctrine delivered at the start of this session \u2014 see \u201CSearch before you create\u201D and \u201CLink by key; never paste another record\u2019s text\u201D.",
     inputSchema: {
       deliverable: external_exports.string().min(1),
       title: external_exports.string().min(1),
@@ -17303,34 +17280,34 @@ Every loose end has one destination, and none of them is prose. Anything you not
       body: markdownSchema.optional()
     }
   }, ({ deliverable, ...fields }) => run(() => client2.promoteDeliverable(deliverable, fields)));
-  registerTool("list_assets", {
+  server2.registerTool("list_assets", {
     description: "List project assets (S3-backed files of any type) filtered by project, status (pending/active/rejected), category (image/video/document), and filename text, sorted by date or size (asc/desc): id, filename, contentType, size, sha256, status, hasThumbnail, and linkCount (live references). Metadata only \u2014 the bytes move by path, never through this result.",
     inputSchema: listAssetsFilterSchema.shape
   }, (args) => run(() => client2.listAssets(args)));
-  registerTool("get_asset", {
+  server2.registerTool("get_asset", {
     description: "Get an asset\u2019s metadata by uuid: filename, contentType, size, sha256 (client-computed, server-verified by read-back), status, hasThumbnail, linkCount (live references), and timestamps. Metadata only \u2014 no value/URL is returned over MCP. To get the bytes, use download_asset (a LOCAL server only \u2014 it writes to a path on the machine running the server) or `ppb assets download`.",
     inputSchema: { asset: uuidSchema }
   }, (args) => run(() => client2.getAsset(args.asset)));
   if (surface === "local") {
-    registerTool("upload_asset", {
+    server2.registerTool("upload_asset", {
       description: "Upload a LOCAL FILE (by path) as a project asset and activate it: reads and SHA-256-hashes the file locally, registers the asset, PUTs the bytes directly to storage, and completes (server verifies the digest by read-back). Returns the asset metadata (status active on success). Only the file PATH crosses the wire \u2014 the bytes never do; do NOT pass base64 or file contents. contentType is guessed from the extension when omitted. Then use link_asset to attach the returned asset to a deliverable revision or a content draft.",
       inputSchema: uploadAssetInputSchema.shape
     }, (args) => run(() => uploadAssetFromPath(client2, apiBaseUrl, args)));
-    registerTool("download_asset", {
+    server2.registerTool("download_asset", {
       description: "Download an ACTIVE asset\u2019s bytes to a LOCAL FILE at `path` (created/overwritten), so you can read or view an uploaded image, mockup, or document. The bytes are written to disk and re-verified against the recorded sha256; the RESULT is metadata + the written path \u2014 never the bytes or a URL. Addressed by asset uuid (from list_assets, get_asset, or get_content).",
       inputSchema: downloadAssetInputSchema.shape
     }, (args) => run(() => downloadAssetToPath(client2, args)));
   }
-  registerTool("link_asset", {
+  server2.registerTool("link_asset", {
     description: "Reference an active asset FROM a target. Two targets are wired: `deliverable_revision` (targetId is a content_deliverable_revision uuid, e.g. from get_content) and `content_draft` (targetId is a content_draft uuid \u2014 the asset attaches to the topic doc and is snapshot-copied onto deliverables when they are created). Rejects a non-active asset or a cross-project link.",
     inputSchema: linkAssetInputSchema.shape
   }, (args) => run(() => client2.linkAsset(args)));
-  registerTool("unlink_asset", {
+  server2.registerTool("unlink_asset", {
     description: "Remove an asset reference by its link id (soft-delete). The asset itself is untouched \u2014 this only drops the reference from its target.",
     inputSchema: unlinkAssetInputSchema.shape
   }, (args) => run(() => client2.unlinkAsset(args.linkId)));
-  registerTool("set_secret", {
-    description: "Create a secret or add a new version under a project + environment (metadata only \u2014 the response NEVER echoes the value). For sensitive values use the `ppb` CLI instead (`ppb secrets set --from-file <f>` or pipe via stdin): a value typed here is placed in the chat transcript before the server can encrypt it. `name` is UPPER_SNAKE_CASE (e.g. API_KEY); `environment` is the environment slug (dev/prod); optional `description`.",
+  server2.registerTool("set_secret", {
+    description: "Create a secret or add a new version under a project + environment (metadata only \u2014 the response NEVER echoes the value). `name` is UPPER_SNAKE_CASE (e.g. API_KEY); `environment` is the environment slug (dev/prod); optional `description`.",
     inputSchema: {
       project: projectKeySchema,
       environment: external_exports.string().min(1),
@@ -17339,14 +17316,14 @@ Every loose end has one destination, and none of them is prose. Anything you not
       description: external_exports.string().optional()
     }
   }, ({ project, environment, name, value, description }) => run(() => client2.setSecret(project, { env: environment, name, value, description })));
-  registerTool("list_secrets", {
+  server2.registerTool("list_secrets", {
     description: "List a project's secrets as METADATA ONLY (id, name, environment, description, current version, timestamps) \u2014 never any value. Optional `environment` slug filter.",
     inputSchema: {
       project: projectKeySchema,
       environment: external_exports.string().min(1).optional()
     }
   }, ({ project, environment }) => run(() => client2.listSecrets(project, { env: environment })));
-  registerTool("describe_secret", {
+  server2.registerTool("describe_secret", {
     description: "Describe one secret: its metadata plus its version history (version, created_at, created_by, and whether each version has been crypto-shredded). METADATA ONLY \u2014 no value is ever returned.",
     inputSchema: {
       project: projectKeySchema,
@@ -17354,8 +17331,8 @@ Every loose end has one destination, and none of them is prose. Anything you not
       name: secretNameSchema
     }
   }, ({ project, environment, name }) => run(() => client2.describeSecret(project, name, { env: environment })));
-  registerTool("rotate_secret", {
-    description: "Rotate an EXISTING secret: store a NEW version and advance the pointer (metadata only \u2014 the response NEVER echoes the value). For sensitive values use the `ppb` CLI instead (`ppb secrets set --from-file <f>` or pipe via stdin): a value typed here is placed in the chat transcript before the server can encrypt it.",
+  server2.registerTool("rotate_secret", {
+    description: "Rotate an EXISTING secret: store a NEW version and advance the pointer (metadata only \u2014 the response NEVER echoes the value).",
     inputSchema: {
       project: projectKeySchema,
       environment: external_exports.string().min(1),
@@ -17363,8 +17340,8 @@ Every loose end has one destination, and none of them is prose. Anything you not
       value: external_exports.string().min(1)
     }
   }, ({ project, environment, name, value }) => run(() => client2.rotateSecret(project, name, { env: environment, value })));
-  registerTool("update_secret_description", {
-    description: "Update a secret's description (metadata-only edit \u2014 does not change the value or add a version).",
+  server2.registerTool("update_secret_description", {
+    description: "Update a secret's description (metadata-only edit \u2014 does not change the value or add a version). Writing guidance for that description lives in the product doctrine delivered at the start of this session.",
     inputSchema: {
       project: projectKeySchema,
       environment: external_exports.string().min(1),
@@ -17372,7 +17349,7 @@ Every loose end has one destination, and none of them is prose. Anything you not
       description: external_exports.string()
     }
   }, ({ project, environment, name, description }) => run(() => client2.updateSecretDescription(project, name, { env: environment, description })));
-  registerTool("delete_secret", {
+  server2.registerTool("delete_secret", {
     description: "Delete a secret: soft-delete the entry and crypto-shred all its versions (the value becomes unrecoverable). Returns confirmation metadata only.",
     inputSchema: {
       project: projectKeySchema,
@@ -17383,14 +17360,14 @@ Every loose end has one destination, and none of them is prose. Anything you not
     await client2.deleteSecret(project, name, { env: environment });
     return { deleted: true, project, environment, name };
   }));
-  registerTool("list_org_instructions", {
-    description: "List the org\u2019s agent instructions \u2014 the per-scope texts appended to this server\u2019s tool descriptions (and, for `general`, its server instructions) at session start. Edits apply to NEW sessions only; use this to see the CURRENT saved values mid-session (at most one row per scope)."
+  server2.registerTool("list_org_instructions", {
+    description: "List the org\u2019s agent instructions \u2014 the per-scope texts this server delivers to a session at start, in its server instructions, under a heading naming each scope. Edits apply to NEW sessions only; use this to see the CURRENT saved values mid-session (at most one row per scope)."
   }, () => run(() => client2.listOrgInstructions()));
-  registerTool("set_org_instruction", {
-    description: "Set (create or replace) one scope\u2019s org-level agent instruction text, max 4000 characters \u2014 over-cap is rejected, never truncated. Scopes: `general` (server-wide), `requirements`, `content`, and `work.<type>` (one per issue type, e.g. `work.epic`). Requires the ADMIN role in the token\u2019s org. Takes effect at the NEXT session start \u2014 running sessions keep the text they launched with. Returns the saved instruction. Organization instructions say how this organization writes, not how Pipebrain works: if a sentence would read identically for an organization that has never met yours, it is product behavior and belongs in the server\u2019s shipped tool descriptions, not here.",
+  server2.registerTool("set_org_instruction", {
+    description: "Set (create or replace) one scope\u2019s org-level agent instruction text, max 4000 characters \u2014 over-cap is rejected, never truncated. Scopes: `general` (server-wide), `requirements`, `content`, and `work.<type>` (one per issue type, e.g. `work.epic`). Requires the ADMIN role in the token\u2019s org. Takes effect at the NEXT session start \u2014 running sessions keep the text they launched with. Returns the saved instruction. Writing guidance for an instruction body lives in the product doctrine delivered at the start of this session \u2014 see \u201CSetting an instruction replaces the whole body\u201D.",
     inputSchema: setOrgInstructionInputSchema.shape
   }, (args) => run(() => client2.setOrgInstruction(args.scope, args.body)));
-  registerTool("delete_org_instruction", {
+  server2.registerTool("delete_org_instruction", {
     description: "Clear one scope\u2019s org-level agent instruction (soft delete; an unset scope is an error naming it). Requires the ADMIN role in the token\u2019s org. Takes effect at the NEXT session start. Returns the cleared instruction.",
     inputSchema: deleteOrgInstructionInputSchema.shape
   }, (args) => run(() => client2.deleteOrgInstruction(args.scope)));
@@ -17459,7 +17436,7 @@ function loadMcpConfig() {
 }
 
 // src/version.ts
-var VERSION = "0.29.0";
+var VERSION = "0.31.0";
 
 // src/main.ts
 var config2 = loadMcpConfig();

package/package.json

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