@thehammer/danx-dashboard-mcp 0.1.165 → 0.1.166

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@thehammer/danx-dashboard-mcp",
-  "version": "0.1.165",
+  "version": "0.1.166",
   "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",
@@ -21,7 +21,7 @@
     "node": ">=20"
   },
   "scripts": {
-    "build": "tsc -p tsconfig.json && node -e \"require('fs').chmodSync('dist/index.js', 0o755)\"",
+    "build": "node -e \"require('fs').rmSync('dist',{recursive:true,force:true})\" && tsc -p tsconfig.json && node -e \"require('fs').chmodSync('dist/index.js', 0o755)\"",
     "verify:boot": "bash scripts/verify-boot.sh",
     "start": "node dist/index.js",
     "dev": "tsx src/index.ts",

package/dist/field-tree.js

@@ -1,45 +0,0 @@
-/**
- * DX-3426 — the shared recursive FIELD-TREE shape.
- *
- * The dashboard's single-card, batch card and plan reads (`danxbot_api`
- * against `GET /api/issues/:id`, `GET /api/issues`, `GET /api/plans/:planId`
- * — DX-3428) take a nested JSON tree instead of a
- * flat field-GROUP list: each key names a field or relation of the resource
- * at that level, and each value is either `true` (the field, or a relation's
- * child with its default fields), a non-negative integer (a cursor-paged
- * relation's own `limit` argument), an opaque cursor STRING (a paged
- * relation's `before` — DX-3428: not every relation's cursor is a plain
- * integer, e.g. a plan event's visibility-scanned row id), a non-empty
- * STRING or ARRAY OF STRINGS (a relation's own declared, non-paging argument
- * — e.g. `records`' `kind`, `events`' `kinds`/`origin`/`writer`), or another
- * field tree (a relation's child with a NAMED field selection). Example:
- *
- *   {"description": true, "ac": true, "problems": {"solutions": {"steps": true}, "decisions": true}, "comments": {"limit": 10}, "records": {"kind": "goal"}}
- *
- * One schema, one module — every tool that accepts a field tree imports THIS
- * export rather than redeclaring the shape, so the recursion is defined once
- * and every caller's JSON Schema serializes the same way. `z.lazy` is
- * required because the schema refers to itself; `zod-to-json-schema` (the
- * MCP SDK's own zod v3 → JSON Schema converter, see
- * `@modelcontextprotocol/sdk`'s `zod-json-schema-compat.ts`) resolves that
- * self-reference to a local `$ref` rather than unrolling it infinitely —
- * verified directly against the listed tool schema in
- * `__tests__/tool-defs.test.ts`, not assumed from reading the library's
- * source. The problem-solutions route's pre-existing `steps` field (DX-3310)
- * is the same `z.lazy` self-reference pattern already shipping on this server.
- */
-import { z } from "zod";
-/**
- * The shared schema. A record whose values are `true`, a non-negative
- * integer, a non-empty string, a non-empty array of non-empty strings, or
- * the same schema recursively — generic on purpose (no issue/plan-specific
- * field names baked in here) so every tool that reads a resource tree
- * reuses it unchanged.
- */
-export const fieldTreeSchema = z.lazy(() => z.record(z.union([
-    z.literal(true),
-    z.number().int().nonnegative(),
-    z.string().min(1),
-    z.array(z.string().min(1)).min(1),
-    fieldTreeSchema,
-])));

package/dist/priority.js

@@ -1,70 +0,0 @@
-/**
- * Tier-word → numeric priority resolution for `danxbot_api`'s
- * `PATCH /api/issues/:id/edit` route (DX-1532).
- *
- * Priority is a STRUCTURED numeric column `issues.priority` (float in `[0,6)`).
- * Both the Trello "priority" label and the dashboard priority badge read it via
- * `priorityTier(issue.priority)` — description PROSE ("Priority: Low") is read
- * by neither. So an agent that "sets priority" by editing description text
- * produces a silent false-positive: nothing downstream changes. The fix is to
- * let the agent write the numeric column through the issue-edit route.
- *
- * Agents (and operators) speak in tier WORDS ("low" / "high"), so the tool
- * accepts a tier word and resolves it to the tier's MIDPOINT here — the inverse
- * of `src/issue-tracker/priority-tier.ts#priorityTier`. A raw numeric is passed
- * through unchanged for the server route to range-validate (it 400s on
- * out-of-`[0,6)`), so the MCP boundary never has to duplicate that bound.
- *
- * This package is a standalone published artifact and cannot import the
- * backend's `priority-tier` module, so the midpoint table is duplicated here.
- * Each value IS the `[min,max)` bucket midpoint by construction and equals the
- * backend's `PRIORITY_TIERS.defaultValue`; `src/issue-tracker/priority-tier.test.ts`
- * asserts `priorityTier(defaultValue) === key` on the canonical side, pinning
- * the round-trip these midpoints rely on.
- */
-/**
- * The six priority tier words, low → high. A const tuple so it doubles as the
- * `z.enum` source in `index.ts`.
- */
-export const PRIORITY_TIER_WORDS = [
-    "lowest",
-    "low",
-    "medium",
-    "high",
-    "very_high",
-    "critical",
-];
-/**
- * Tier word → bucket midpoint (inverse of `priorityTier`). Lands the numeric
- * column squarely inside the requested tier so a later `priorityTier` read
- * returns the same word.
- */
-export const PRIORITY_TIER_MIDPOINTS = {
-    lowest: 0.5,
-    low: 1.5,
-    medium: 2.5,
-    high: 3.5,
-    very_high: 4.5,
-    critical: 5.5,
-};
-/**
- * Resolve a priority input — a tier WORD or a raw numeric — to the numeric
- * value the `PATCH /api/issues/:id/edit` route stores in `issues.priority`.
- *
- * - tier word → its bucket midpoint (`PRIORITY_TIER_MIDPOINTS`).
- * - number → passed through unchanged; the server route range-validates it to
- *   `[0,6)` and 400s otherwise (the MCP boundary deliberately does not
- *   re-validate the bound — single source of truth on the route).
- * - unknown string → throws here at the MCP boundary (no round-trip). The Zod
- *   enum on the tool schema already rejects this for tool callers; the explicit
- *   throw keeps the helper safe for any direct caller.
- */
-export function resolvePriority(input) {
-    if (typeof input === "number")
-        return input;
-    const midpoint = PRIORITY_TIER_MIDPOINTS[input];
-    if (midpoint === undefined) {
-        throw new Error(`issue-edit: unknown priority tier word "${input}" (expected one of ${PRIORITY_TIER_WORDS.join(", ")} or a number in [0,6))`);
-    }
-    return midpoint;
-}