wolfpack-mcp 1.0.81 → 1.0.83

package/dist/client.js

@@ -612,8 +612,10 @@ export class WolfpackClient {
         return this.api.post(`/subscriptions/${documentType}/${documentId}/unmute`, {});
     }
     // Discussion methods
-    async getDiscussions(documentType, documentId) {
-        return this.api.get(`/discussions/${documentType}/${documentId}`);
+    async getDiscussions(documentType, documentId, teamSlug) {
+        // A document ID is only unique within a project, so the server has to be told
+        // which one is meant rather than searching them all
+        return this.api.get(this.withTeamSlug(`/discussions/${documentType}/${documentId}`, teamSlug));
     }
     async getDiscussionByComment(commentId) {
         return this.api.get(`/discussions/by-comment/${commentId}`);

package/dist/index.js

@@ -645,6 +645,10 @@ const UUID_FIELDS_TO_STRIP = new Set([
 const GetDiscussionsSchema = z.object({
     document_type: z.string().describe('Document type (e.g. "wiki", "work_item", "issue")'),
     document_id: z.string().describe('The ID of the document'),
+    project_slug: z
+        .string()
+        .optional()
+        .describe('Project slug — a document ID is only unique within one project'),
 });
 const GetDiscussionByCommentSchema = z.object({
     comment_id: z
@@ -862,10 +866,14 @@ class WolfpackMCPServer {
                             'Call this before updating to see current content. ' +
                             'WORKFLOW: When asked to work on an item, check its status and follow the required state transitions ' +
                             '(pending→pull first, new→doing, review→doing when you are picking the work back up, ' +
-                            'blocked/ready/completed/closed→new→doing, then review when done). ' +
+                            'ready/completed/closed→new→doing, then review when done). ' +
+                            'AGENTS: a "blocked" item is not yours to restart — a human clears the blocker. Leave it where it is, ' +
+                            'comment if you can help clear it, and take the next claimable item instead. ' +
                             'PLANNING: Check if the description contains a plan (markdown checklist). If not, APPEND one using update_work_progress - preserve all original description text and add your plan below a "---" separator. ' +
                             'FORMS: Procedure-created work items may include formDefinition (field definitions with name, label, type, required, options) and formValues (current values). Use submit_work_item_form to fill in form values. ' +
                             'REVIEW CHECKS: items under review may carry review checks (code-review, security-review, ...); see list_work_item_checks and claim/complete_work_item_check. ' +
+                            'DEPENDENCIES: dependsOn lists the work this item follows and nextItems the work that follows it, each with satisfied=true once it has finished. ' +
+                            'An item with an unsatisfied entry in dependsOn cannot be pulled yet — take the work it depends on first. ' +
                             'IMAGES: Image references in the description (e.g. `![alt](/api/files/...)`) can be viewed using the download_image tool.',
                         inputSchema: {
                             type: 'object',
@@ -913,6 +921,7 @@ class WolfpackMCPServer {
                             'STATUS WORKFLOW: "pending" (backlog) → "new" (to do) → "doing" (in progress) → "review" (work done) → "ready" (awaiting deployment) → "completed" (deployed). ' +
                             'Use "blocked" when work cannot proceed. AGENTS: you cannot start un-started work here — ' +
                             'a status change on a "pending" or "new" item that is not assigned to you is refused. ' +
+                            'Nor can you move an item OUT of "blocked": clearing a blocker is a human decision. ' +
                             'Take it with pull_work_item, which assigns it to you and puts it in "doing"; that is ' +
                             'what makes the board show who is working on what. ' +
                             'When moving to "review", add a completion comment via create_work_item_comment. When moving to "blocked", add a comment explaining the blocker. ' +
@@ -1018,6 +1027,8 @@ class WolfpackMCPServer {
                             'now — so there is no separate "move it to doing" step. Move it to "review" when done. ' +
                             'AGENTS: with more than one item claimable, take them in the order list_work_items gives ' +
                             'you: bug fixes first, then higher priority, then oldest. ' +
+                            'AGENTS: an item waiting on unfinished work it depends on is not claimable and will return ' +
+                            '403 naming what to take first — see dependsOn on get_work_item. ' +
                             'If no assignee is specified, assigns to the API key owner. ' +
                             'In personal projects, items are always assigned to the owner.',
                         inputSchema: {
@@ -1068,6 +1079,7 @@ class WolfpackMCPServer {
                         description: 'List review checks (key controls such as code-review, security-review, e2e-review) on work items. ' +
                             'With work_item_id: every check on that item. Without it: your REVIEWER INBOX — pending checks on ' +
                             'work items in the work pools you belong to that are unclaimed or held by you, each with workItemRefId and workItemTitle. ' +
+                            'Checks on blocked items are left out — blocked work is not picked up, and claiming one is refused. ' +
                             'REVIEW WORKFLOW: claim a check with claim_work_item_check, get_work_item to read the work, review it, ' +
                             'then complete_work_item_check with "passed" or "failed" and a short summary. ' +
                             'A failed check sends the item back to its developer with your summary as feedback; do not change the item status yourself.',
@@ -2100,6 +2112,10 @@ class WolfpackMCPServer {
                                     type: 'string',
                                     description: 'The ID of the document',
                                 },
+                                project_slug: {
+                                    type: 'string',
+                                    description: 'Project slug — a document ID is only unique within one project',
+                                },
                             },
                             required: ['document_type', 'document_id'],
                         },
@@ -3069,7 +3085,7 @@ class WolfpackMCPServer {
                     // Discussion handlers
                     case 'get_discussions': {
                         const parsed = GetDiscussionsSchema.parse(args);
-                        const result = await this.client.getDiscussions(parsed.document_type, parsed.document_id);
+                        const result = await this.client.getDiscussions(parsed.document_type, parsed.document_id, parsed.project_slug);
                         return {
                             content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
                         };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wolfpack-mcp",
-  "version": "1.0.81",
+  "version": "1.0.83",
   "description": "MCP server for Wolfpack AI-enhanced software delivery tools",
   "main": "dist/index.js",
   "type": "module",