@thehammer/danx-dashboard-mcp 0.1.250 → 0.1.252

package/dist/index.js

@@ -632,6 +632,7 @@ strictTool("request_permission", "Ask a person to grant this key ONE MORE permis
 // a different reason: it MAKES a plan rather than acting on one, so there is
 // no existing plan for an id to name yet.
 strictTool("plan_connect", 
+// DX-4493 — the `naming` block carries the thread title the session must take before it connects.
 // DX-4318 — states only what to do with the reply. What it used to add arrives where it is used: a rejected
 // action's rule in the event line itself (`listen.ts`), the mantra in the reply's own `reminders[]` text.
 // DX-4390 — signed out, this is also how the session asks for access.
@@ -644,7 +645,7 @@ 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 reply's `naming` block (status `needed`) gives your `{Name}: PLAN-NNN {short " +
+    "takes no plan id. 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()

package/dist/lifecycle.js

@@ -252,7 +252,7 @@ export function registerLifecycleTools(strictTool) {
         "register the Slack mirror so future card updates re-render the thread's card-view message. Thread " +
         "scope is IMPLICIT (channel + thread_ts come from the dispatch) — pass only the issue id. Call this " +
         "AFTER posting your substantive answer with danxbot_slack_reply (that reply becomes the card-view " +
-        '"message #1"). A second call on an already-linked thread fails loud with a 409 — never a silent re-link.', { issue_id: z.string().describe('The card id to bind this thread to (e.g. "DX-1086").') }, async (args) => {
+        '"message #1"). A second call on an already-linked thread fails loud with a 409 — never a silent re-link.', { issue_id: z.string().describe('The card id to bind this thread to (e.g. "ABC-123").') }, async (args) => {
         const url = readLifecycleUrlsFromEnv().linkThreadToIssue;
         if (!url)
             throw new Error("link_thread_to_issue called outside a Slack dispatch");
@@ -310,10 +310,11 @@ export function registerLifecycleTools(strictTool) {
             .enum(["Bug", "Story", "Chore"])
             .describe("The card type. Never Epic/Feature — a single Slack request never warrants a container card."),
         title: z.string().describe("Card title."),
+        // DX-4515: the create route refuses a card with no summary.
         summary: z
             .string()
             .min(1)
-            .describe("REQUIRED (DX-4515): one plain line saying what the card is, shown at the top of the card page."),
+            .describe("REQUIRED: one plain line saying what the card is, shown at the top of the card page."),
         description: z
             .string()
             .describe("Card description — sourced from the triggering human message's content."),
@@ -397,7 +398,7 @@ export function registerLifecycleTools(strictTool) {
     strictTool("request_code_review", "TERMINAL for this dispatch — call it when your diff is done and its own tests are green, instead of " +
         "danxbot_complete. Pushes your branch (card/<id> to origin/card/<id>), then dispatches every code " +
         "gate this card carries as its OWN independent gate-reviewer dispatch (you never sign or review your " +
-        "own diff — DX-3741). Ends this dispatch 'completed' and releases the card to ToDo; when the card is " +
+        "own diff). Ends this dispatch 'completed' and releases the card to ToDo; when the card is " +
         "re-dispatched to you, read its quality_gates (through danxbot_api): every code gate pass/skipped → " +
         "run agent-finalize.sh and complete normally; any fail → fix its findings, then call " +
         "request_code_review again (never sign or remove a code gate yourself — removal is refused, 409). " +

package/package.json

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