@thehammer/danx-dashboard-mcp 0.1.199 → 0.1.200

package/dist/danxbot-api-examples.js

@@ -12,6 +12,10 @@
  * a 4xx on three writes: a card create without `plan`, an edit whose `ac[]`
  * items were keyed `text` (and one with no `content_hash`), and a retro whose
  * flag was false but whose description was missing, then prose.
+ * DX-3917 / DX-4015 — the phase D run found 9 work sessions writing the
+ * retro before the `complete` transition (the list went AC tick -> retro,
+ * with no transition between) and 14 of 24 writing the transition with no
+ * spec call: the transition is now a shown write, placed before the retro.
  *
  * Kept as data, not prose, so danxbot's own tests can check each example
  * against the live server contract (route table, resource fields, body
@@ -49,6 +53,11 @@ export const DANXBOT_API_EXAMPLES = {
         path: "/api/issues/<id>/checklists/<checklists[].id>/items/<items[].id>",
         body: { status: "passing" },
     },
+    transition: {
+        method: "POST",
+        path: "/api/issues/<id>/transition",
+        body: { action: "<action>", summary: "<text>" },
+    },
     retro: {
         method: "PUT",
         path: "/api/issues/<id>/retro",
@@ -78,6 +87,7 @@ export function danxbotApiExamplesText() {
         `card edit ${render(e.cardEdit)} (only the keys you change; \`ac\` replaces the list); ` +
         `comment ${render(e.comment)}; ` +
         `AC tick ${render(e.acTick)}; ` +
-        `retro ${render(e.retro)} (description "" unless the flag is true; ` +
+        `transition ${render(e.transition)}; ` +
+        `retro, only after \`complete\` or \`cancel\`, ${render(e.retro)} (description "" unless the flag is true; ` +
         `\`tests[].kind\` ${RETRO_TEST_KIND_EXAMPLES.map((k) => `"${k}"`).join(" or ")}).`);
 }

package/dist/index.js

@@ -340,10 +340,11 @@ const boardField = {
 // ---------------- danxbot_api (DX-3465, PLN-11 R-25) ----------------
 strictTool("danxbot_api", "Call any dashboard API route your credential may reach. `method` + `path` (a FULL path, e.g. " +
     '"/api/issues/DX-1/transition" — substitute real ids yourself, never a route template with `:id` in it) + ' +
+    // DX-3997 — `reminders[]` also relays the dashboard's own listener reminder
+    // to a plan-connected session; the reminder's text explains itself.
     "optional `query`/`body`. The response is the route's JSON body verbatim, `reminders[]` included when the " +
-    "route attaches one — a plan-connected session whose event listener the dashboard reports unattached also gets " +
-    "the dashboard's own `plan_list.listener_unattached` reminder relayed there (DX-3997). `board` overrides this dispatch's configured board for a board-scoped route only " +
-    "(ignored by a route that isn't board-scoped). See this server's own instructions (shown once, at connect) " +
+    "route attaches one. `board` overrides this dispatch's configured board for a board-scoped route only. " +
+    "See this server's own instructions (shown once, at connect) " +
     "for the shared resource shape, the stale-hash rule, and how to read a refusal — don't know the route? call " +
     "`danxbot_api_list` first. " +
     // DX-4015 — the ONE statement of which writes need a spec call first; the

package/package.json

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