@thehammer/danx-dashboard-mcp 0.1.188 → 0.1.189

package/dist/index.js

@@ -422,7 +422,7 @@ strictTool("attach_file", "Attach a LOCAL file to a card: `card_id` + `path` (an
 // no existing plan for an id to name yet.
 strictTool("plan_connect", 
 // DX-2735: trimmed with the problem tools to stay inside the work-profile budget.
-"Connect THIS session to a plan. ONE CALL IS ENOUGH TO START: the reply carries `{session, movedFrom, browserInstruction, briefing, listenerHealth}` — `browserInstruction` is a server-built action to take NOW: it names the plan's URL and tells you to open it (in-app browser if you have one, else default), keep that tab open for the whole session without navigating it away, and use a different tab for your own browsing — the operator's tab for following and talking to you. Returned on every connect, including a re-connect, so it doubles as the post-context-loss reminder. `briefing` is every goal/rule/caveat (ref+body), every architecture section (id+title), the plan's own ref/name/status, a first page of open cards (id/type/status/title/openProblemCount/assignedAgent) with a `morePagesHint` when more exist, and the closed-card count — usually replacing the plan read + card batch-read a fresh session used to need. A session is on AT MOST ONE plan: connecting elsewhere MOVES it, and `movedFrom: {id, name} | null` says which plan it left (null = no plan, or already this one). Binds only your OWN session, resolved from the session id this server forwards; afterwards a `danxbot_api` call to a `/api/plans/mine/...` route (there is no dedicated plan-write tool) acts on this plan and takes no plan id. `listenerHealth` reports the event bridge's state — `null` (no session), or `{attached, state: \"unattached\"|\"credential_mismatch\"|\"healthy\", nextStep}` naming a concrete fix per unhealthy state (same shape the plan list/get routes report). Once healthy, every comment, answer, problem added and block/unblock on this plan's cards reaches the session unpolled, relayed by the plugin's event bridge as a line like `[DX-8 \"Title\" repo:board] newms87 answered \"<statement>\": chose \"Pause E2E\"`. Pass `title` (call `get_session({session_id:\"self\"})` first and forward its `title` verbatim) so the dashboard shows the same name Claude does — this server cannot read it itself. The response's `reminders[]` (when present) carries the mantra — read and follow it.", {
+"Connect THIS session to a plan. ONE CALL IS ENOUGH TO START: the reply carries `{session, movedFrom, browserInstruction, briefing, listenerHealth}` — `browserInstruction` is a server-built action to take NOW: it names the plan's URL and tells you to open it (in-app browser if you have one, else default), keep that tab open for the whole session without navigating it away, and use a different tab for your own browsing — the operator's tab for following and talking to you. Returned on every connect, including a re-connect, so it doubles as the post-context-loss reminder. `briefing` is every goal/rule/caveat (ref+body), every architecture section (id+title), the plan's own ref/name/status, a first page of open cards (id/type/status/title/openProblemCount/assignedAgent) with a `morePagesHint` when more exist, and the closed-card count — usually replacing the plan read + card batch-read a fresh session used to need. A session is on AT MOST ONE plan: connecting elsewhere MOVES it, and `movedFrom: {id, name} | null` says which plan it left (null = no plan, or already this one). Binds only your OWN session, resolved from the session id this server forwards; afterwards a `danxbot_api` call to a `/api/plans/mine/...` route (there is no dedicated plan-write tool) acts on this plan and takes no plan id. `listenerHealth` reports the event bridge's state — `null` (no session), or `{attached, state: \"unattached\"|\"credential_mismatch\"|\"healthy\", nextStep}` naming a concrete fix per unhealthy state (same shape the plan list/get routes report). Once healthy, every comment, answer, problem added and block/unblock on this plan's cards reaches the session unpolled, relayed by the plugin's event bridge as a line like `[DX-8 \"Title\" repo:board] newms87 answered \"<statement>\": chose \"Pause E2E\"`. An action the operator DECLINES arrives as `... rejected the action \"<title>\" for \"<statement>\" — reason: \"<note>\". Do not perform it; re-plan from the reason` (a decision with `outcome: \"rejected\"` — never treat it as work done). Pass `title` (call `get_session({session_id:\"self\"})` first and forward its `title` verbatim) so the dashboard shows the same name Claude does — this server cannot read it itself. The response's `reminders[]` (when present) carries the mantra — read and follow it.", {
     plan_id: z.number().int().positive().describe("The plan id, from the plans list (`danxbot_api` `GET /api/plans`)."),
     title: z
         .string()

package/dist/listen.js

@@ -78,6 +78,27 @@ function isRecord(value) {
 function isCappedText(value) {
     return isRecord(value) && typeof value.text === "string" && typeof value.truncated === "boolean";
 }
+/**
+ * DX-3880 — the part `solution_answered` and `problem_answer_changed` share: the
+ * decision's `outcome` and the either/or body it implies. A rejection (the
+ * operator DECLINED an action) always names the solution and carries its reason
+ * as `solution.note`; an answer is a solution (optional note) or free-form text.
+ */
+function invalidDecisionBody(d) {
+    if (d.outcome !== "answered" && d.outcome !== "rejected")
+        return 'detail.outcome is not "answered" or "rejected"';
+    if (d.solution === null) {
+        if (d.outcome === "rejected")
+            return "detail.solution is null on a rejection";
+        return isCappedText(d.freeform) ? null : "detail.freeform is not capped text";
+    }
+    if (!isRecord(d.solution) || typeof d.solution.title !== "string")
+        return "detail.solution is not {title, note}";
+    if (d.outcome === "rejected") {
+        return isCappedText(d.solution.note) ? null : "detail.solution.note (the rejection reason) is not capped text";
+    }
+    return d.solution.note === null || isCappedText(d.solution.note) ? null : "detail.solution.note is not capped text";
+}
 /**
  * DX-2735 — why an event cannot be described, or `null` when it can.
  *
@@ -122,11 +143,7 @@ export function invalidEventReason(value) {
             if (!isRecord(problem) || typeof problem.id !== "number" || !isCappedText(problem.statement)) {
                 return "detail.problem is not {id, statement}";
             }
-            if (d.solution === null)
-                return isCappedText(d.freeform) ? null : "detail.freeform is not capped text";
-            if (!isRecord(d.solution) || typeof d.solution.title !== "string")
-                return "detail.solution is not {title, note}";
-            return d.solution.note === null || isCappedText(d.solution.note) ? null : "detail.solution.note is not capped text";
+            return invalidDecisionBody(d);
         }
         case "problem_added": {
             const problem = d.problem;
@@ -155,11 +172,7 @@ export function invalidEventReason(value) {
                 return "detail.retracted_decision_id is not a number";
             if (typeof d.decision_id !== "number")
                 return "detail.decision_id is not a number";
-            if (d.solution === null)
-                return isCappedText(d.freeform) ? null : "detail.freeform is not capped text";
-            if (!isRecord(d.solution) || typeof d.solution.title !== "string")
-                return "detail.solution is not {title, note}";
-            return d.solution.note === null || isCappedText(d.solution.note) ? null : "detail.solution.note is not capped text";
+            return invalidDecisionBody(d);
         }
         case "blocked":
             return isCappedText(d.reason) ? null : "detail.reason is not capped text";
@@ -196,8 +209,13 @@ function describe(event) {
             // so the line names the problem — otherwise the agent cannot tell which of its
             // questions just closed.
             const problem = d.problem;
-            const answered = `${who} answered ${quoted(problem.statement)}:`;
             const solution = d.solution;
+            // DX-3880 — a REJECTION is the opposite of work done: the operator declined
+            // the action, so the line says so and names the reason; the agent must not
+            // perform it and re-plans from the note.
+            if (d.outcome === "rejected")
+                return `${who} rejected the action "${solution.title}" for ${quoted(problem.statement)} — reason: ${quoted(solution.note)}. Do not perform it; re-plan from the reason`;
+            const answered = `${who} answered ${quoted(problem.statement)}:`;
             if (solution === null)
                 return `${answered} ${quoted(d.freeform)}`;
             const note = solution.note === null ? "" : ` — note: ${quoted(solution.note)}`;
@@ -222,6 +240,8 @@ function describe(event) {
             // open questions knows which one just moved.
             const problem = d.problem;
             const solution = d.solution;
+            if (d.outcome === "rejected")
+                return `${who} changed the answer to ${quoted(problem.statement)}: now REJECTED the action "${solution.title}" — reason: ${quoted(solution.note)}. Do not perform it; re-plan from the reason`;
             const now = solution === null ? quoted(d.freeform) : `"${solution.title}"`;
             return `${who} changed the answer to ${quoted(problem.statement)}: now ${now}`;
         }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@thehammer/danx-dashboard-mcp",
-  "version": "0.1.188",
+  "version": "0.1.189",
   "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, danxbot_complete, and other per-dispatch lifecycle callbacks) (DX-3465, PLN-11 R-25).",
   "license": "MIT",
   "type": "module",