pipebrain-mcp 0.47.1 → 0.48.1

package/dist/main.js

@@ -15521,6 +15521,15 @@ var issueSchema = external_exports.object({
   // An absent field and an unmarked issue would be indistinguishable to a caller, which
   // is precisely the failure the wire mappers in libs/db/src/issues.ts warn about.
   reservedForPerson: external_exports.boolean(),
+  // Whether the issue's PROJECT has been archived (PIPE-419). Derived on read from the
+  // project's own `deleted_at`, never stored on the issue — archiving a project touches
+  // no issue row, which is exactly why the flag has to be carried rather than inferred.
+  //
+  // REQUIRED for the same reason `reservedForPerson` above is: both mappers send it on
+  // every issue, and this schema is a `z.object`, so an undeclared key is stripped in
+  // silence rather than rejected — a field left off here would vanish from anything that
+  // parses through it with nothing to say it had.
+  projectArchived: external_exports.boolean(),
   source: sourceSchema,
   metadata: metadataSchema,
   customFields: customFieldsSchema,
@@ -15921,22 +15930,6 @@ var orgInstructionSchema = external_exports.object({
   body: external_exports.string().min(1),
   createdBy: uuidSchema.nullable(),
   viaTokenId: uuidSchema.nullable(),
-  /**
-   * sha256 of the shipped default this row was SEEDED from, or null when nothing seeded
-   * it — a row written by a person, a row re-created after its scope was cleared, or a row
-   * that predates seeding.
-   *
-   * It is what lets a settings page say the shipped default has MOVED since this
-   * organization got it, without the product ever applying that move: comparing this digest
-   * against the running release's default for the same scope is the whole signal. It is not
-   * updated by an edit, because what it records is what was seeded — which stays true after
-   * the organization rewrites the body, and is exactly then that the comparison is worth
-   * making.
-   *
-   * `.default(null)` rather than a bare nullable, for the tolerance this schema keeps
-   * throughout: a payload from a server that predates the column still parses.
-   */
-  seededDefaultSha: external_exports.string().nullable().default(null),
   createdAt: external_exports.iso.datetime({ offset: true }),
   updatedAt: external_exports.iso.datetime({ offset: true }),
   deletedAt: external_exports.iso.datetime({ offset: true }).nullable()
@@ -16605,12 +16598,6 @@ var listEnvelopeSchema = (item) => external_exports.object({ items: external_exp
 var mintedTokenSchema = apiTokenSchema.extend({ token: external_exports.string().min(1) }).loose();
 var tokenListSchema = listEnvelopeSchema(apiTokenSchema);
 var orgInstructionListSchema = listEnvelopeSchema(orgInstructionSchema);
-var instructionDefaultSchema = external_exports.object({
-  scope: external_exports.string().min(1),
-  body: external_exports.string().min(1),
-  sha256: external_exports.string().min(1)
-}).loose();
-var instructionDefaultListSchema = listEnvelopeSchema(instructionDefaultSchema);
 var ApiClient = class _ApiClient {
   baseUrl;
   auth;
@@ -17354,18 +17341,6 @@ var ApiClient = class _ApiClient {
     const body = await this.request("GET", "/api/v1/org-instructions", {}, orgInstructionListSchema);
     return body.items;
   }
-  /**
-   * The starting text THIS RELEASE ships, per scope, with the digest a seeded row records.
-   *
-   * Shipped content rather than the org's, so it carries no tenant data and any
-   * authenticated caller may read it. Comparing a row's `seededDefaultSha` against the
-   * `sha256` here is how a settings page says the shipped default has MOVED since this
-   * organization was seeded — a difference the product reports and never applies.
-   */
-  async listInstructionDefaults() {
-    const body = await this.request("GET", "/api/v1/org-instructions/defaults", {}, instructionDefaultListSchema);
-    return body.items;
-  }
   /** Upserts one scope's instruction text (ADMIN+; body ≤ 4000 chars). */
   setOrgInstruction(scope, body) {
     return this.request("PUT", `/api/v1/org-instructions/${enc(scope)}`, { body: { body } }, orgInstructionSchema);
@@ -17905,7 +17880,7 @@ function createMcpServer(baseClient, apiBaseUrl, orgInstructions2 = /* @__PURE__
     (args) => run(() => client2().listIssues(args), GUIDANCE_POINTER)
   );
   registerStrict("get_issue", {
-    description: `Full issue detail by display id or uuid: the header \u2014 \`summary\`, \`why\`, \`affectedSurfaces\`, with \`headerDerivedAt\` and \`headerStale\`, true when nobody has written a header or the body has moved since one was written, and \`set_issue_header\` is what writes it \u2014 body, criteria (states, modes, evidence), explicit requirement links (pinned revision + staleness), the project\u2019s cross-cutting requirements at their latest approved revision, this organization\u2019s approved conventions \u2014 standing guidance that BINDS work in every project here, delivered in full at the revision a person approved \u2014 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. Long records read in PARTS: \`bodyOffset\`/\`bodyLimit\` window the body (UTF-16 offsets; parts concatenate back exactly), \`commentOffset\`/\`commentLimit\` window the oldest-first comment list. Unpaged, the body is capped at ${ISSUE_BODY_CHAR_LIMIT} chars and comments at the newest ${ISSUE_COMMENT_LIMIT}; a response that left anything out says so in \`omitted\` \u2014 the true totals, the omitted comment count, and in \`next\` the exact arguments for the adjacent part (body walks forward, comments toward older) \u2014 follow \`next\` until null to retrieve everything. An issue under both caps reads whole in ONE call, no notice.`,
+    description: `Full issue detail by display id or uuid: the header \u2014 \`summary\`, \`why\`, \`affectedSurfaces\`, with \`headerDerivedAt\` and \`headerStale\`, true when nobody has written a header or the body has moved since one was written, and \`set_issue_header\` is what writes it \u2014 body, criteria (states, modes, evidence), explicit requirement links (pinned revision + staleness), the project\u2019s cross-cutting requirements at their latest approved revision, this organization\u2019s approved conventions \u2014 standing guidance that BINDS work in every project here, delivered in full at the revision a person approved \u2014 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. Carries \`projectArchived\` on the same terms: true when the project is retired, so this read still answers while lists, search and the work-moving writes do not. 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. Long records read in PARTS: \`bodyOffset\`/\`bodyLimit\` window the body (UTF-16 offsets; parts concatenate back exactly), \`commentOffset\`/\`commentLimit\` window the oldest-first comment list. Unpaged, the body is capped at ${ISSUE_BODY_CHAR_LIMIT} chars and comments at the newest ${ISSUE_COMMENT_LIMIT}; a response that left anything out says so in \`omitted\` \u2014 the true totals, the omitted comment count, and in \`next\` the exact arguments for the adjacent part (body walks forward, comments toward older) \u2014 follow \`next\` until null to retrieve everything. An issue under both caps reads whole in ONE call, no notice.`,
     inputSchema: getIssueInputSchema.shape,
     // The same result-threshold annotation `get_work_context` declares, and the same
     // key spelled out for the same reason (an unknown `_meta` key is silently
@@ -18341,7 +18316,7 @@ function loadMcpConfig() {
 }
 
 // src/version.ts
-var VERSION = "0.47.1";
+var VERSION = "0.48.1";
 
 // src/main.ts
 async function scopedClient(base, org) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pipebrain-mcp",
-  "version": "0.47.1",
+  "version": "0.48.1",
   "description": "Pipebrain MCP server for Claude Code and Claude Desktop — issues, requirements, decision records, conventions, prompts, content, assets, metadata-only secrets, and more of the platform's modules over the Pipebrain API.",
   "type": "module",
   "license": "MIT",