@thehammer/danx-dashboard-mcp 0.1.219 → 0.1.220

package/dist/lifecycle.js

@@ -214,15 +214,15 @@ export function registerLifecycleTools(strictTool) {
     });
     // ---------------- danxbot_slack_reply ----------------
     const slackReply = strictTool("danxbot_slack_reply", "Post the FINAL user-facing reply to the originating Slack thread. Call exactly once per dispatch, " +
-        "immediately before danxbot_complete. Optionally attach result files via files[] (absolute paths of files on YOUR own " +
-        "disk — their bytes are uploaded, so this works whichever host the dashboard runs on) — text + attachments " +
+        "immediately before danxbot_complete. Optionally attach result files via files[] (absolute paths on your own disk; " +
+        "bytes are uploaded, so any host works) — text + attachments " +
         "land as ONE atomic thread post. For intermediate " +
         "progress use danxbot_slack_post_update instead.", {
         text: z.string().describe("The final reply text to post to the Slack thread."),
         files: z
             .array(z.string())
             .optional()
-            .describe("Optional absolute paths of files on your own disk to attach; their bytes are uploaded."),
+            .describe("Absolute paths of your own files to attach; bytes are uploaded."),
     }, async (args) => {
         const url = readLifecycleUrlsFromEnv().slackReply;
         if (!url)

package/package.json

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