@thehammer/danx-dashboard-mcp 0.1.303 → 0.1.304

package/dist/index.js

@@ -398,7 +398,7 @@ function readSessionConfig() {
  */
 const SERVER_INSTRUCTIONS = `\
 \`danxbot_api\` is your primary channel to the dashboard: every card, plan, Slack and dispatch-callback job (ending
-your dispatch included) is a call to it. Find a route with \`danxbot_api_list\`. Read its exact shape with
+yours too) is a call to it. Find a route with \`danxbot_api_list\`. Read its exact shape with
 \`danxbot_api_spec\` before the first call to any route you have not called before; never guess a body.
 
 RESOURCES. Most collections take GET (list) and POST (create); a single resource (\`<collection>/<id>\`) takes
@@ -407,7 +407,7 @@ GET, PATCH or PUT (send only the fields you change) and DELETE. A card is edited
 \`total\` (page with \`limit\` and \`offset\`). Name each other field or relation you need in the \`fields\` query
 tree. \`GET /api/resources/<resource>/fields\` lists the names.
 
-STALE HASH. A write to contested text (a card's title, description or checklists, a plan record, a problem) sends
+STALE HASH. A write to contested text (card text, a plan record, a problem) sends
 back the \`content_hash\` or \`base_hash\` you read from that resource. A stale hash is refused 409 with the current
 hash and content: merge your change into that and retry with the fresh hash.
 
@@ -417,8 +417,11 @@ REFUSALS. A 4xx body is \`{error, ...}\`, and its other fields name the fix: \`o
 WRITING STANDARD, for every title, summary, description, comment, problem, solution and plan record you write. The
 reader is new to the subject and will not read the code or docs: what you write is their documentation. Open with
 plain background (what the thing is, why it exists, what is wrong or what the choice changes) before evidence.
-Define each term a newcomer would not know. Cite exact ids, SHAs and paths. Be brief: less to read, never a
-transcript of your reasoning. A title or summary alone must let the reader decide.
+Define each term a newcomer would not know. Cite exact ids, SHAs and paths. Be brief; never transcribe your
+reasoning. A title or summary alone must let the reader decide.
+
+DESIGN. UI designs and style options go on a Design card (\`design_publish\`), never an Artifact or HTML page.
+Decide choices yourself; show alternatives as design states, never ask.
 `;
 assertWithinTextLimit("the server instructions", SERVER_INSTRUCTIONS);
 export const server = new McpServer({

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@thehammer/danx-dashboard-mcp",
-  "version": "0.1.303",
+  "version": "0.1.304",
   "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, request_permission, attach_file, and danxbot_slack_reply) (DX-3465, PLN-11 R-25).",
   "license": "MIT",
   "type": "module",