@thehammer/danx-dashboard-mcp 0.1.83 → 0.1.84

package/dist/handlers.js

@@ -392,7 +392,11 @@ export async function issueComment(client, args) {
         return client.request({
             method: "POST",
             path: `/${idEnc}/comments`,
-            body: { text, ...(args.metadata !== undefined ? { metadata: args.metadata } : {}) },
+            body: {
+                text,
+                ...(args.metadata !== undefined ? { metadata: args.metadata } : {}),
+                ...(args.problem_id !== undefined ? { problem_id: args.problem_id } : {}),
+            },
             board,
         });
     }

package/dist/index.js

@@ -504,12 +504,13 @@ server.tool("issue_triage", "Record a triage confidence score via POST /api/issu
     ...boardField,
 }, async (args) => jsonResult(await issueTriage(client, args)));
 // ---------------- issue_comment ----------------
-server.tool("issue_comment", "Comment CRUD via /api/issues/:id/comments[/:cid]. action=add → POST {text, metadata?} (server stamps author from bearer + auto-incrementing ordinal); action=edit → PATCH /:cid {text}; action=delete → DELETE /:cid (soft-delete, audit trail preserved — comments are NEVER hard-deleted). Client-supplied author is IGNORED (server-stamped to prevent impersonation). `metadata` (DX-2157, action=add only) is an OPTIONAL opaque JSON object a calling app attaches to the comment — e.g. a generated `{sql, explanation}` packet its own UI renders specially. danxbot stores + returns it verbatim and enforces NO shape on its contents; omit for a plain markdown-only comment (unaffected either way).", {
+server.tool("issue_comment", "Comment CRUD via /api/issues/:id/comments[/:cid]. action=add → POST {text, metadata?, problem_id?} (server stamps author from bearer + auto-incrementing ordinal); action=edit → PATCH /:cid {text}; action=delete → DELETE /:cid (soft-delete, audit trail preserved — comments are NEVER hard-deleted). Client-supplied author is IGNORED (server-stamped to prevent impersonation). `metadata` (DX-2157, action=add only) is an OPTIONAL opaque JSON object a calling app attaches to the comment — e.g. a generated `{sql, explanation}` packet its own UI renders specially. danxbot stores + returns it verbatim and enforces NO shape on its contents; omit for a plain markdown-only comment (unaffected either way). `problem_id` (DX-2906, action=add only) OPTIONALLY threads the comment as a follow-up question under one of this SAME card's problems (from `issue_problem` list/add) WITHOUT answering it — commenting never changes open_problem_count, blocked, or records a decision; use issue_problem's answer route for that. An unknown id, another card's id, or a removed problem's id all 404 naming the problem id — an ANSWERED (but not removed) problem still accepts a follow-up comment, since the thread continues after a decision.", {
     id: z.string().min(1),
     action: z.enum(["add", "edit", "delete"]),
     comment_id: z.number().int().positive().optional(),
     text: z.string().min(1).optional(),
     metadata: z.record(z.unknown()).optional(),
+    problem_id: z.number().int().positive().optional().describe("action=add only — thread this comment as a follow-up under a LIVE problem of this same card, without answering it"),
     ...boardField,
 }, async (args) => jsonResult(await issueComment(client, args)));
 // ---------------- issue_checklist ----------------

package/dist/listen.js

@@ -92,8 +92,18 @@ export function invalidEventReason(value) {
     if (!isRecord(d))
         return "detail is not an object";
     switch (value.kind) {
-        case "comment_added":
-            return isCappedText(d.excerpt) ? null : "detail.excerpt is not capped text";
+        case "comment_added": {
+            if (!isCappedText(d.excerpt))
+                return "detail.excerpt is not capped text";
+            // DX-2906 — `problem` is OPTIONAL (only present when the comment named
+            // one); absent is valid, but a present-and-malformed one is not.
+            if (d.problem === undefined)
+                return null;
+            const problem = d.problem;
+            return isRecord(problem) && typeof problem.id === "number" && isCappedText(problem.statement)
+                ? null
+                : "detail.problem is not {id, statement}";
+        }
         case "solution_answered": {
             const problem = d.problem;
             if (!isRecord(problem) || typeof problem.id !== "number" || !isCappedText(problem.statement)) {
@@ -122,8 +132,16 @@ export function invalidEventReason(value) {
 function describe(event) {
     const d = event.detail;
     switch (event.kind) {
-        case "comment_added":
-            return `${event.actor} commented: ${quoted(d.excerpt)}`;
+        case "comment_added": {
+            // DX-2906 — a comment naming a problem (a follow-up question, without
+            // answering it) relays distinctly from a plain comment, so an agent
+            // listening to the stream can tell which of its open problems just
+            // got a reply.
+            const problem = d.problem;
+            if (problem === undefined)
+                return `${event.actor} commented: ${quoted(d.excerpt)}`;
+            return `${event.actor} commented on problem ${quoted(problem.statement)}: ${quoted(d.excerpt)}`;
+        }
         case "solution_answered": {
             // DX-2735: every answer answers ONE problem on a card that may carry several,
             // so the line names the problem — otherwise the agent cannot tell which of its

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@thehammer/danx-dashboard-mcp",
-  "version": "0.1.83",
+  "version": "0.1.84",
   "description": "Stdio MCP server wrapping danxbot's dashboard /api/issues/* normalized DB-backed HTTP routes for dispatched agents (DX-704 Phase 2).",
   "license": "MIT",
   "type": "module",