@thehammer/danx-dashboard-mcp 0.1.338 → 0.1.339

package/dist/listen.js

@@ -135,6 +135,9 @@ export function invalidEventReason(value) {
         case "comment_added": {
             if (!isCappedText(d.excerpt))
                 return "detail.excerpt is not capped text";
+            // DX-5435: the line tells the agent which comment to signal on, so a person's comment must name it.
+            if (isPersonsComment(value) && typeof d.comment_id !== "number")
+                return "detail.comment_id is not a number";
             // 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)
@@ -227,6 +230,19 @@ function actorLabel(event) {
     const via = event.viaKey === null ? "" : ` via ${event.viaKey.name}`;
     return `${event.actor}${via} (${event.origin})`;
 }
+/** DX-5435: a comment a person wrote (not the session's own pause notice, not an agent's or the machine's): the one an agent should signal it is answering. */
+function isPersonsComment(event) {
+    return event.origin === "operator" && event.release !== true;
+}
+/**
+ * DX-5435: what the agent does first with a person's comment. The responding signal shows the person "<agent> is responding..." under their comment in
+ * the Comments drawer until the agent's reply lands. The text is written here, with the line the agent reads, so every session that updates this package
+ * sends the signal without a plugin change.
+ */
+export function respondingInstruction(cardId, commentId) {
+    const path = `/api/issues/${cardId}/comments/${commentId}/responding`;
+    return `If you will answer it, first call danxbot_api POST ${path} (no body) so the person sees you are on it; if you then decide no reply is needed, DELETE the same path`;
+}
 /** Only ever called on an event `invalidEventReason` accepted, so its casts are checked. */
 function describe(event) {
     const d = event.detail;
@@ -240,9 +256,10 @@ function describe(event) {
             const problem = d.problem;
             if (event.release === true)
                 return `${who} notice: ${quoted(d.excerpt)}`;
+            const respond = isPersonsComment(event) ? `. ${respondingInstruction(event.cardId, d.comment_id)}` : "";
             if (problem === undefined)
-                return `${who} commented: ${quoted(d.excerpt)}`;
-            return `${who} commented on problem ${quoted(problem.statement)}: ${quoted(d.excerpt)}`;
+                return `${who} commented: ${quoted(d.excerpt)}${respond}`;
+            return `${who} commented on problem ${quoted(problem.statement)}: ${quoted(d.excerpt)}${respond}`;
         }
         case "solution_answered": {
             // DX-2735: every answer answers ONE problem on a card that may carry several,

package/dist/plan-events-relay.js

@@ -176,7 +176,7 @@ export class PlanEventRelay {
             this.start(cursor);
         if (this.buffer.length > 0)
             return this.answer();
-        // DX-5415 / DX-4233: supersede where the waiter is installed, not before the pauses: calls resume in call order, so the newest always holds the slot and an older one that resumed late cannot orphan the waiter beneath it.
+        // DX-5415 / DX-4233: supersede where the waiter is installed, not only before the pauses, so an older call that resumed late cannot orphan the waiter beneath it. Calls resume in call order because a settle (capped at FINAL_SETTLE_BOUND_MS) ends before the idle window (HEARTBEAT_ACTIVITY_WINDOW_MS) can chain a second one; a wall-clock jump can break that order, costing the newer caller one early empty answer, never a second waiter.
         this.supersedeWaiter();
         return new Promise((resolve) => {
             const onAbort = () => this.supersedeWaiter();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@thehammer/danx-dashboard-mcp",
-  "version": "0.1.338",
+  "version": "0.1.339",
   "description": "Stdio MCP server fronting danxbot's dashboard API for agents (operator sessions and dispatched workers alike): the generic danxbot_api/danxbot_api_list/danxbot_api_spec tools reach any route the caller's credential may call, plus dedicated agent-specific tools (plan_connect, request_permission, attach_file, and danxbot_slack_reply) (DX-3465, PLN-11 R-25).",
   "license": "MIT",
   "type": "module",