@thehammer/danx-dashboard-mcp 0.1.240 → 0.1.241

package/dist/index.js

@@ -555,11 +555,8 @@ strictTool("plan_connect",
     "titles and a first page of open cards) and `listenerHealth` (when its `state` is not `healthy`, do its " +
     "`nextStep`). A session is on at most one plan: connecting elsewhere moves it, and `movedFrom` names the " +
     "plan it left. Afterwards a `danxbot_api` call to a `/api/plans/mine/...` route acts on this plan and " +
-    "takes no plan id. DX-4493 — a connected session's title must be `{Name}: PLAN-NNN {short title}`: the " +
-    "reply's `naming` block (`status: needed`: `format`, `instruction`, `suggestedTitle`, `liveNames`; `ok`: " +
-    "nothing to do) gives the exact title. Rename this thread to it (desktop `set_session_title`; terminal: ask " +
-    "the person to `/rename`), then connect again with that exact `title`. A wrong format or a name another live " +
-    "session holds is refused.", {
+    "takes no plan id. DX-4493: a reply's `naming` block (status `needed`) gives your `{Name}: PLAN-NNN {short " +
+    "title}`; rename this thread to it (`set_session_title`, or ask for `/rename`), then connect again with that `title`.", {
     plan_id: z
         .number()
         .int()
@@ -570,7 +567,7 @@ strictTool("plan_connect",
         .string()
         .min(1)
         .optional()
-        .describe('Only the exact title from the previous reply\'s `naming` block (`{Name}: PLAN-NNN {short title}`), after you renamed this thread to it. Omit on the first connect.'),
+        .describe('The `naming` block\'s exact `{Name}: PLAN-NNN {short title}`, after renaming this thread. Omit on the first connect.'),
     disconnect: z.boolean().optional().describe("true = leave `plan_id` (your current plan); no `title`."),
 }, 
 // DX-2862 — the connect is also the moment this session's event bridge learns

package/package.json

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