wolfpack-mcp 1.0.77 → 1.0.79

package/README.md

@@ -232,7 +232,8 @@ Get a specific issue.
 
 #### `create_issue`
 
-Create a new issue.
+Create a new issue. Human callers only — issues are how the people using the product report problems
+they hit, so an agent files what it finds with `create_work_item` instead.
 
 - `title` (required): Issue title
 - `description`, `severity`, `type`, `assigned_to_id`, `environment`, `affected_version`, `reproducible`,

package/dist/apiClient.js

@@ -1,4 +1,4 @@
-import fetch from 'node-fetch';
+import { fetch } from './proxyFetch.js';
 import { config } from './config.js';
 export class ApiError extends Error {
     status;

package/dist/index.js

@@ -13,6 +13,7 @@ import { AGENT_BUILDER_TOOLS, handleAgentBuilderTool } from './agentBuilderTools
 import { PROCEDURE_TOOLS, handleProcedureTool } from './procedureTools.js';
 import { AGENT_SELF_TOOLS, handleAgentSelfTool } from './agentSelfTools.js';
 import { resolveRadarItemId } from './resolveRadarItemId.js';
+import { fetch as proxyFetch } from './proxyFetch.js';
 // Get current package version
 const require = createRequire(import.meta.url);
 const packageJson = require('../package.json');
@@ -21,7 +22,10 @@ const PACKAGE_NAME = packageJson.name;
 // Check for updates from npm registry
 async function checkForUpdates() {
     try {
-        const response = await fetch(`https://registry.npmjs.org/${PACKAGE_NAME}/latest`, {
+        // proxyFetch, not global fetch: in a restricted container the registry is
+        // only reachable through the proxy, and a direct attempt just stalls until
+        // the timeout on every start (#1793).
+        const response = await proxyFetch(`https://registry.npmjs.org/${PACKAGE_NAME}/latest`, {
             headers: { Accept: 'application/json' },
             signal: AbortSignal.timeout(5000), // 5 second timeout
         });
@@ -828,7 +832,8 @@ class WolfpackMCPServer {
                             'Returns full details including description (markdown notes). ' +
                             '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, blocked/ready/completed/closed→new→doing, then review when done). ' +
+                            '(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). ' +
                             '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. ' +
                             'IMAGES: Image references in the description (e.g. `![alt](/api/files/...)`) can be viewed using the download_image tool.',
@@ -850,7 +855,7 @@ class WolfpackMCPServer {
                     {
                         name: 'update_work_progress',
                         description: 'Update work item description/notes with your progress. WORKFLOW: 1) get_work_item to read current notes 2) Modify the markdown description with new findings/progress 3) Call this with the complete updated description. The full description replaces the existing one. ' +
-                            'STATUS: Items in "new" are auto-advanced to "doing" (updating progress means work has started). Completing the work is NOT auto-detected: when done, set status to "review" via update_work_item and add a completion comment. ' +
+                            'STATUS: Items in "new" — and items in "review" you are picking back up — are auto-advanced to "doing" (recording progress means work is under way). Completing the work is NOT auto-detected: when done, set status to "review" via update_work_item and add a completion comment. ' +
                             'CRITICAL: NEVER overwrite or remove the original description text. Preserve all existing content exactly as-is. Append your plan below a "---" separator. You may only modify content you previously added (your plan section). ' +
                             'BEST PRACTICE: Append a plan with markdown checkboxes (- [ ] task). Check off completed tasks (- [x] task) as you progress. Include sections for: Plan (checklist), Approach (strategy), and Notes (discoveries/decisions). ' +
                             CONTENT_LINKING_HELP,
@@ -881,6 +886,7 @@ class WolfpackMCPServer {
                             '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. ' +
+                            'When you take an item back out of "review" to rework it, set it to "doing" first — an item being changed is not an item waiting to be reviewed. ' +
                             'closing_comment is only accepted together with status "closed" — never use it for progress or completion notes.',
                         inputSchema: {
                             type: 'object',
@@ -1271,6 +1277,7 @@ class WolfpackMCPServer {
                     {
                         name: 'create_issue',
                         description: 'Create a new issue in your current project (auto-selected for single-project users, or use list_projects first for multi-project). Requires mcp:issues:create permission. ' +
+                            'Agents: not for you. Issues are how the people using the product report problems they hit — file what you found with create_work_item instead. ' +
                             CONTENT_LINKING_HELP,
                         inputSchema: {
                             type: 'object',
@@ -2136,12 +2143,16 @@ class WolfpackMCPServer {
                         let workItem = await this.client.updateWorkProgress(parsed.work_item_id, parsed.description, teamSlug);
                         if (workItem) {
                             let summary = `Updated description on: ${workItem.title}`;
-                            // Progress on a "new" item means work has started — advance it to "doing"
-                            if (workItem.status === 'new') {
-                                const advanced = await this.client.updateWorkItem(parsed.work_item_id, { status: 'doing' }, teamSlug);
+                            // Recording progress means the work is under way: a "new" item starts, and an
+                            // item in "review" comes back to "doing" because its developer is working on it
+                            // again (#1787) — otherwise the board keeps showing handed-over work that is
+                            // still being changed.
+                            const previousStatus = workItem.status;
+                            if (previousStatus === 'new' || previousStatus === 'review') {
+                                const advanced = await this.moveToDoing(parsed.work_item_id, teamSlug);
                                 if (advanced) {
                                     workItem = advanced;
-                                    summary += ' (status auto-advanced new → doing)';
+                                    summary += ` (status auto-advanced ${previousStatus} → doing)`;
                                 }
                             }
                             let text = `${summary}\n\n${JSON.stringify(stripUuids(workItem), null, 2)}`;
@@ -2971,6 +2982,24 @@ class WolfpackMCPServer {
             }
         });
     }
+    /**
+     * Put a work item in "doing" after progress was recorded on it, and report whether that
+     * stuck. An agent whose work pool may not set "doing" — a reviewer annotating an item in
+     * "review" rather than the developer resuming it — is refused by the backend status
+     * policy; that refusal is the right answer, so it leaves the saved note alone instead of
+     * failing the call the agent actually made.
+     */
+    async moveToDoing(workItemId, teamSlug) {
+        try {
+            return await this.client.updateWorkItem(workItemId, { status: 'doing' }, teamSlug);
+        }
+        catch (error) {
+            if (error && typeof error === 'object' && 'status' in error && error.status === 403) {
+                return null;
+            }
+            throw error;
+        }
+    }
     isImageBuffer(buffer) {
         if (buffer.length < 4)
             return false;

package/dist/proxyFetch.js

@@ -0,0 +1,61 @@
+import nodeFetch from 'node-fetch';
+import { HttpProxyAgent } from 'http-proxy-agent';
+import { HttpsProxyAgent } from 'https-proxy-agent';
+/**
+ * Whether a host is exempted from proxying by NO_PROXY. Entries match the host
+ * exactly or as a domain suffix (`.example.com`, or bare `example.com` for its
+ * subdomains); `*` exempts everything.
+ */
+export function bypassesProxy(hostname, noProxy) {
+    if (!noProxy)
+        return false;
+    const host = hostname.toLowerCase();
+    return noProxy
+        .split(',')
+        .map((entry) => entry.trim().toLowerCase())
+        .filter(Boolean)
+        .some((entry) => {
+        if (entry === '*')
+            return true;
+        const suffix = entry.startsWith('.') ? entry : `.${entry}`;
+        return host === entry.replace(/^\./, '') || host.endsWith(suffix);
+    });
+}
+/** The proxy URL that applies to a target, or null to connect directly. */
+export function proxyForUrl(target, env = process.env) {
+    if (bypassesProxy(target.hostname, env.NO_PROXY ?? env.no_proxy))
+        return null;
+    const proxy = target.protocol === 'https:'
+        ? (env.HTTPS_PROXY ?? env.https_proxy ?? env.HTTP_PROXY ?? env.http_proxy)
+        : (env.HTTP_PROXY ?? env.http_proxy);
+    return proxy || null;
+}
+const agents = new Map();
+function agentFor(target) {
+    const proxy = proxyForUrl(target);
+    if (!proxy)
+        return undefined;
+    const key = `${target.protocol}${proxy}`;
+    let agent = agents.get(key);
+    if (!agent) {
+        agent = target.protocol === 'https:' ? new HttpsProxyAgent(proxy) : new HttpProxyAgent(proxy);
+        agents.set(key, agent);
+    }
+    return agent;
+}
+/**
+ * `node-fetch` with the proxy from the environment applied.
+ *
+ * node-fetch does not read HTTP_PROXY/HTTPS_PROXY on its own, so inside a
+ * restricted agent container this client connected direct to the backend —
+ * which has no route out and no DNS, the container's only permitted egress
+ * being the Squid proxy (#1793). Agents are cached per origin, and requests
+ * are unaffected when no proxy variables are set.
+ */
+export function fetch(url, init = {}) {
+    if (init.agent !== undefined)
+        return nodeFetch(url, init);
+    const target = new URL(typeof url === 'string' ? url : url.url);
+    return nodeFetch(url, { ...init, agent: agentFor(target) });
+}
+export default fetch;

package/dist/proxyFetch.test.js

@@ -0,0 +1,67 @@
+import { afterEach, beforeEach, describe, expect, it } from 'vitest';
+import { createServer } from 'node:http';
+import { once } from 'node:events';
+import { bypassesProxy, fetch, proxyForUrl } from './proxyFetch.js';
+const port = (server) => server.address().port;
+describe('bypassesProxy', () => {
+    it('exempts an exact host and its subdomains, on a dot boundary only', () => {
+        expect(bypassesProxy('localhost', 'localhost,127.0.0.1')).toBe(true);
+        expect(bypassesProxy('api.example.com', '.example.com')).toBe(true);
+        expect(bypassesProxy('example.com', 'example.com')).toBe(true);
+        expect(bypassesProxy('notexample.com', 'example.com')).toBe(false);
+        expect(bypassesProxy('wolfpacks.work', 'localhost,127.0.0.1')).toBe(false);
+    });
+    it('treats * as exempting everything, and no NO_PROXY as exempting nothing', () => {
+        expect(bypassesProxy('wolfpacks.work', '*')).toBe(true);
+        expect(bypassesProxy('wolfpacks.work', undefined)).toBe(false);
+    });
+});
+describe('proxyForUrl', () => {
+    it('prefers HTTPS_PROXY for https and falls back to HTTP_PROXY', () => {
+        const env = { HTTPS_PROXY: 'http://s:1', HTTP_PROXY: 'http://p:2' };
+        expect(proxyForUrl(new URL('https://wolfpacks.work/api'), env)).toBe('http://s:1');
+        expect(proxyForUrl(new URL('http://wolfpacks.work/api'), env)).toBe('http://p:2');
+        expect(proxyForUrl(new URL('https://wolfpacks.work/api'), { HTTP_PROXY: 'http://p:2' })).toBe('http://p:2');
+    });
+    it('returns null for a NO_PROXY host and when no proxy is configured', () => {
+        expect(proxyForUrl(new URL('http://localhost:3001/api'), {
+            NO_PROXY: 'localhost',
+            HTTP_PROXY: 'http://p:1',
+        })).toBeNull();
+        expect(proxyForUrl(new URL('https://wolfpacks.work/api'), {})).toBeNull();
+    });
+});
+describe('fetch', () => {
+    let proxy;
+    let seen;
+    beforeEach(async () => {
+        seen = [];
+        proxy = createServer((req, res) => {
+            seen.push(req.url ?? '');
+            res.writeHead(200, { 'content-type': 'application/json' });
+            res.end('{"proxied":true}');
+        });
+        proxy.listen(0);
+        await once(proxy, 'listening');
+    });
+    afterEach(() => {
+        proxy.close();
+        delete process.env.HTTP_PROXY;
+        delete process.env.NO_PROXY;
+    });
+    // Regression test for #1793: node-fetch does not read the proxy variables,
+    // so inside a restricted container this client connected direct to a backend
+    // it had neither a route to nor DNS for.
+    it('sends the request to the proxy, for a host it cannot itself resolve', async () => {
+        process.env.HTTP_PROXY = `http://127.0.0.1:${port(proxy)}`;
+        const res = await fetch('http://nowhere.invalid/api/mcp/work-items');
+        expect(res.status).toBe(200);
+        expect(seen).toEqual(['http://nowhere.invalid/api/mcp/work-items']);
+    });
+    it('connects direct when no proxy is configured', async () => {
+        const res = await fetch(`http://127.0.0.1:${port(proxy)}/direct`);
+        expect(res.status).toBe(200);
+        // Reached the server as an origin request, not as a proxy request
+        expect(seen).toEqual(['/direct']);
+    });
+});

package/dist/workItemReminders.js

@@ -25,6 +25,9 @@ const STATUS_REMINDERS = {
         'BEFORE starting work.',
     doing: 'REMINDER: This work item is in "doing". The moment the work is complete, set status to "review" ' +
         '(update_work_item) and add a completion comment — do not leave it sitting in "doing".',
+    review: 'REMINDER: This work item is in "review" — the work was handed over. If you are picking it back ' +
+        'up (rework, review feedback, a follow-up change), set status to "doing" (update_work_item) BEFORE ' +
+        'starting, so the board shows the work is under way again. If you are reviewing it, leave it where it is.',
 };
 // Reminders to prepend to a get_work_item response, most urgent first.
 export function getWorkItemReminders(status, description, approved) {

package/dist/workItemReminders.test.js

@@ -50,13 +50,18 @@ describe('getWorkItemReminders', () => {
             expect.stringContaining('set status to "review"'),
         ]);
     });
+    it('tells agents picking a reviewed item back up to move it to doing', () => {
+        const reminders = getWorkItemReminders('review', PLAN);
+        expect(reminders).toEqual([expect.stringContaining('set status to "doing"')]);
+        expect(reminders[0]).toContain('If you are reviewing it, leave it where it is');
+    });
     it('adds the no-plan reminder when the description has no plan', () => {
         const reminders = getWorkItemReminders('new', 'Just a description');
         expect(reminders).toHaveLength(2);
         expect(reminders[1]).toContain('no plan');
     });
     it('stays quiet for statuses with no required action', () => {
-        expect(getWorkItemReminders('review', PLAN)).toEqual([]);
         expect(getWorkItemReminders('completed', PLAN)).toEqual([]);
+        expect(getWorkItemReminders('ready', PLAN)).toEqual([]);
     });
 });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wolfpack-mcp",
-  "version": "1.0.77",
+  "version": "1.0.79",
   "description": "MCP server for Wolfpack AI-enhanced software delivery tools",
   "main": "dist/index.js",
   "type": "module",
@@ -35,6 +35,8 @@
   },
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.26.0",
+    "http-proxy-agent": "^7.0.2",
+    "https-proxy-agent": "^7.0.6",
     "node-fetch": "^3.3.2",
     "yaml": "^2.8.0",
     "zod": "^3.24.1"