@thehammer/danx-dashboard-mcp 0.1.209 → 0.1.211

package/README.md

@@ -29,7 +29,7 @@ There is no dedicated `resource_fields` tool (removed DX-3465 — it was a thin
 
 A dedicated tool survives only for something about the agent itself, never a card/plan operation: `plan_connect` (binds the session to a plan; the event-bridge hook keys on it) and the per-dispatch worker callbacks (`danxbot_complete`, `danxbot_slack_reply`, `danxbot_slack_post_update`, `load_template_app`/`save_template_app`, `quality_gate_complete`, `link_thread_to_issue`, `attach_file`, the `slack_recovery_*` trio, `danxbot_set_evaluator_summary`) — see `src/lifecycle.ts`. The live list is always `tool-defs.json` in this package, regenerated by `npm run gen-tool-defs` — read it rather than trusting a list copied into prose.
 
-Card and plan reads/writes go through `danxbot_api` against the issue/plan route families documented in `GET /api/openapi` (via `danxbot_api_spec`) — `POST /api/issues`, `GET /api/issues/:id` (or `/batch` for many at once, DX-2727), `PATCH /api/issues/:id/edit`, `POST /api/issues/:id/transition`, the problems/solutions/dependencies/comments/quality-gates/retro sub-resource routes, and the equivalent `/api/plans/*` family (`GET /api/plans/:planId` — cheap scalars by default, `fields` opts into `cards`/`records`/`architecture`/`sessions`; `GET /api/plans` for the list, with an optional `status` filter over the same computed `complete`/`awaiting-session`/`building`/`planning` value `GET /api/plans/:planId` always returns ungated).
+Card and plan reads/writes go through `danxbot_api` against the issue/plan route families documented in `GET /api/openapi` (via `danxbot_api_spec`) — `POST /api/issues`, `GET /api/issues/:id` (or `/batch` for many at once, DX-2727), `PATCH /api/issues/:id/edit`, `POST /api/issues/:id/transition`, the problems/solutions/dependencies/comments/quality-gates/retro sub-resource routes, and the equivalent `/api/plans/*` family (`GET /api/plans/:planId` — cheap scalars by default, `fields` opts into `cards`/`records`/`architecture`/`session_history`/`worker_dispatches`; `GET /api/plans` for the list, with an optional `status` filter over the same computed `complete`/`awaiting-session`/`building`/`planning` value `GET /api/plans/:planId` always returns ungated).
 
 ## `bridge` — a working session's event stream client
 

package/dist/index.js

@@ -249,8 +249,7 @@ EXACT current shape of the one(s) you picked, before calling them through \`danx
 schema, required permission, and every documented error envelope. Never guess a field name or a route path.
 
 ALWAYS PASS \`fields\`. The default response for a list/get route is minimal — scalars only, no relations, no
-heavy text. Every resource that supports it takes a \`fields\` query param (a field tree, or a flat group list on
-an older route) that opts into exactly what you need. Passing nothing and then being surprised a field is
+heavy text. Every resource that supports it takes a \`fields\` query param (a JSON field tree) that opts into exactly what you need. Passing nothing and then being surprised a field is
 missing is a caller bug, not a server one — check the spec for the resource's own field vocabulary.
 
 THE STALE-HASH RULE. A write that touches contested text (a card's title/description/checklists, a plan

package/dist/listen.js

@@ -323,6 +323,32 @@ export function formatNudgeLine(event) {
         "Work these cards; any you cannot work, update to its true state: open a problem, add depends_on or " +
         "conflict_on, block it with the real reason, or rollback_pickup.");
 }
+/** Why a reminder cannot be read, or `null` when it can. */
+export function invalidReminderReason(value) {
+    if (!isRecord(value))
+        return "the reminder is not an object";
+    if (value.kind !== "policy_reminder")
+        return "kind is not policy_reminder";
+    if (typeof value.text !== "string" || value.text.trim() === "")
+        return "text is not a non-empty string";
+    return null;
+}
+/**
+ * The label every reminder carries, so the session can never read one as the operator speaking
+ * (DX-2955: "labelled unmistakably as automated system reminders, never phrased as the operator").
+ */
+export const REMINDER_LABEL = "AUTOMATED SYSTEM REMINDER from the danxbot dashboard monitor (not from the operator):";
+/**
+ * The text of a reminder: the label, then the reminder as the dashboard wrote it. Unlike an
+ * activity line the body keeps its line breaks, because a reminder with something off is the
+ * numbered checklist plus what is off. Throws, naming the fault, on a malformed reminder.
+ */
+export function formatReminderLine(event) {
+    const invalid = invalidReminderReason(event);
+    if (invalid !== null)
+        throw new Error(`malformed reminder event: ${invalid}`);
+    return `${LINE_PREFIX} ${REMINDER_LABEL}\n${event.text.trim()}`;
+}
 /**
  * Incremental SSE parser. Comment lines (keep-alives, the connect marker) and
  * field-less blocks produce no message, which is what keeps them out of the output.
@@ -463,6 +489,25 @@ export async function runListener(options, deps) {
             deps.write({ type: "event", id: null, text, origin: null });
             return null;
         }
+        if (message.event === "reminder") {
+            // DX-2955 - like a nudge: no usable id, never replayed, never deduplicated, and
+            // `origin: null` so `bridge.ts` delivers it immediately instead of folding it
+            // into a digest (the generic null-origin exemption in `routeEvent`).
+            let parsed;
+            let invalid;
+            try {
+                parsed = JSON.parse(message.data);
+                invalid = invalidReminderReason(parsed);
+            }
+            catch (err) {
+                invalid = `not JSON: ${err.message}`;
+            }
+            const text = invalid === null
+                ? formatReminderLine(parsed)
+                : `${LINE_PREFIX} could not read reminder (${invalid}): ${oneLine(message.data, 300)}`;
+            deps.write({ type: "event", id: null, text, origin: null });
+            return null;
+        }
         if (message.event !== "activity")
             return null;
         // `Number(null)` is 0, so a frame with no id must never be read as event 0: that id

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@thehammer/danx-dashboard-mcp",
-  "version": "0.1.209",
+  "version": "0.1.211",
   "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",