@thehammer/danx-dashboard-mcp 0.1.194 → 0.1.196

package/dist/index.js

@@ -345,7 +345,12 @@ strictTool("danxbot_api", "Call any dashboard API route your credential may reac
     "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) " +
     "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; unsure of its exact shape? call `danxbot_api_spec` first. " +
+    "`danxbot_api_list` first. " +
+    // DX-4015 — the ONE statement of which writes need a spec call first; the
+    // `work` profile's spec-first sentence defers to this list. A shown write
+    // is copied from its example (3 of 3 canary sessions did, with zero 4xx).
+    "Before your first write to a route not shown below, and always before `PUT /api/issues/:id/retro`, " +
+    "call `danxbot_api_spec`. " +
     // DX-3923 — the shapes agents guessed wrong most often, shown before the
     // first call instead of learned from a 4xx.
     danxbotApiExamplesText(), {

package/package.json

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