@thehammer/danx-dashboard-mcp 0.1.152 → 0.1.154

package/README.md

@@ -21,7 +21,7 @@ All exposed as `mcp__danx-dashboard__<name>` once wired through the workspace `m
 
 | Tool | HTTP | Notes |
 |---|---|---|
-| `issue_list` | `GET /api/issues` | filters: `type`, `parent_id` (null → root-only), `dispatchable_derived`, `assigned_agent`, `include_closed`, `limit`, `offset` |
+| `issue_list` | `GET /api/issues` | filters: `type`, `parent_id` (null → root-only), `dispatchable_derived`, `assigned_agent`, `include_closed`, `limit`, `offset`. `fields` (DX-3427) is the SAME recursive field tree `issue_get` takes, against the same issue resource — list-row fields (`ac_total`, `comments_count`, `waiting_on`, `quality_gates`, `next_pre_gate`, …) sit alongside every detail field. See `resource_fields` |
 | `issue_get` | `GET /api/issues/:id` or `GET /api/issues/batch` | Pass `id` for one card, or `ids[]` (DX-2727, at most 100) to resolve many across boards in ONE call — global, so `ids` with `board` throws; per-id `not_found` rather than a whole-call 404. Minimal scalars by default; `fields` (DX-3426) opts in via a recursive field TREE — `{"description": true, "problems": {"solutions": true}, "comments": {"limit": 10}}` — not a flat group list; a cursor-paged relation (today only `comments`) takes its page args (`limit`/`before`) inside its own nested object, so paging now works on the batch form too. See `resource_fields` |
 | `resource_fields` | `GET /api/resources/:resource/fields` | DX-3426 — what an `issue_get`-style field tree may name for one resource: `{resource, description, always, hashes, fields, relations}`. Install-global, no `board`. `resource: "issue"` is the root; a relation's own `resource` in the response is what to call this again with, one level deeper |
 | `issue_create` | `POST /api/issues` | Epic REQUIRES non-empty `phase_children[]` (atomic insert). `title` = short domain-naming label; `summary` = 1–3 plain-language sentences, always shown; `description` = the collapsed "Context" body. Root and every phase child take their own `summary` |

package/dist/handlers.js

@@ -25,19 +25,21 @@ import { readFile } from "node:fs/promises";
 import { basename, extname, isAbsolute } from "node:path";
 import { resolvePriority } from "./priority.js";
 /**
- * `filter`/`fields`/`sort` are JSON/CSV-encoded onto the query string (the
- * route parses `?filter=<JSON>`, `?fields=a,b`, `?sort=<JSON>` — see
- * `src/issues/read/reader.ts#parseEnvelope`); each is omitted entirely when
- * empty so the wire carries no `{}`/`[]` noise. `board` stays a flat
- * top-level param, resolved by the HTTP client exactly as before.
+ * `filter`/`fields`/`sort` are JSON-encoded onto the query string (the route
+ * parses `?filter=<JSON>`, `?fields=<JSON>`, `?sort=<JSON>` — see
+ * `src/issues/read/reader.ts#parseEnvelope` + `handleGetIssues`); each is
+ * omitted entirely when empty so the wire carries no `{}`/`[]` noise. `board`
+ * stays a flat top-level param, resolved by the HTTP client exactly as
+ * before.
  */
 export async function issueList(client, args) {
     const query = {};
     if (args.filter !== undefined && Object.keys(args.filter).length > 0) {
         query.filter = JSON.stringify(args.filter);
     }
-    if (args.fields !== undefined && args.fields.length > 0) {
-        query.fields = args.fields.join(",");
+    // DX-3427 — a JSON-encoded field tree, mirroring `issue_get` below.
+    if (args.fields !== undefined && Object.keys(args.fields).length > 0) {
+        query.fields = JSON.stringify(args.fields);
     }
     if (args.sort !== undefined && args.sort.length > 0) {
         query.sort = JSON.stringify(args.sort);

package/dist/index.js

@@ -277,25 +277,6 @@ const EFFORT_VALUES = [
 // still be CREATED through this MCP.
 const ISSUE_TYPES = ["Epic", "Bug", "Feature", "Story", "Chore", "Task"];
 const NON_EPIC_TYPES = ["Bug", "Feature", "Story", "Chore", "Task"];
-// DX-935 / DX-937 — field-group taxonomy for the LIST read envelope,
-// hand-copied from `src/issues/read/field-groups.ts` (`LIST_GROUPS` — this
-// package cannot import server source). Drift surfaces at runtime as a server
-// 400, not silently. DX-3426 moved `issue_get` to the field tree
-// (`field-tree.ts`); DX-3427 moves the list the same way and deletes this.
-const LIST_FIELD_GROUPS = [
-    "description",
-    // DX-2735: replaced the flat "solutions" group (hard cut, no alias).
-    "problems",
-    "ac",
-    "comments",
-    "retro",
-    "dependencies",
-    "triage",
-    "assignment",
-    "quality_gates",
-    "children",
-    "effort",
-];
 const SORT_ORDERS = ["asc", "desc"];
 const sortField = z
     .array(z.object({
@@ -360,7 +341,7 @@ const MARKDOWN_STYLE_DESCRIBE = "Renders as markdown here. Use `##`/`###` header
 strictTool("issue_list", 
 // DX-2735: trimmed to pay for the problem tools inside the work-profile
 // injected-surface budget — same facts, no repeated prose.
-"List cards. Board-scoped; see `board`. `filter`: type, parent_id, dispatchable_derived, status_derived[], self_dispatchable_derived, assigned_agent, include_closed, include_deleted, q (free text over id+title+description). THE DEFAULT ROW IS MINIMAL — scalars only (id, type, title, status, parent_id, priority, created_at, updated_at, assigned_agent, content_hash), no joins; opt into heavy data with `fields` groups: description (+ summary), problems (open_problem_count — a card needs a human exactly when this is > 0), ac, comments, retro, dependencies, triage, assignment, quality_gates, children, effort. `sort`: [{column, order}] over id|priority|repo_name|title|type|status_derived|triage_ice_total|created_at|updated_at (default order: see `sort`'s own field description). `limit`/`offset` page (uncapped by default). `include_closed` defaults to FALSE: a bare call silently excludes every Done/Cancelled card (leaf AND container alike). The response always carries `total` (the full count matching every filter except limit/offset — compare against `issues.length` to tell an exhausted list from a truncated one) and, whenever `include_closed` was not explicitly `true`, `closed_excluded` (how many additional terminal cards the default withheld — re-call with `include_closed: true` to see them). issue_get reads one card in full.", {
+"List cards. Board-scoped; see `board`. `filter`: type, parent_id, dispatchable_derived, status_derived[], self_dispatchable_derived, assigned_agent, include_closed, include_deleted, q (free text over id+title+description). THE DEFAULT ROW IS MINIMAL — scalars only (id, type, title, status, parent_id, priority, created_at, updated_at, assigned_agent, content_hash), no joins; `fields` opts into more — the SAME recursive field-tree JSON `issue_get` takes, against the SAME issue resource (list-row fields like `ac_total`/`comments_count`/`waiting_on`/`quality_gates`/`next_pre_gate` sit alongside every detail field `issue_get` can name). Call `resource_fields({resource:\"issue\"})` for the full, current list of what `fields` may name — never guess a name; unknown → 400 `unknown_field`. `sort`: [{column, order}] over id|priority|repo_name|title|type|status_derived|triage_ice_total|created_at|updated_at (default order: see `sort`'s own field description). `limit`/`offset` page (uncapped by default). `include_closed` defaults to FALSE: a bare call silently excludes every Done/Cancelled card (leaf AND container alike). The response always carries `total` (the full count matching every filter except limit/offset — compare against `issues.length` to tell an exhausted list from a truncated one) and, whenever `include_closed` was not explicitly `true`, `closed_excluded` (how many additional terminal cards the default withheld — re-call with `include_closed: true` to see them). issue_get reads one card in full.", {
     filter: z
         .object({
         q: z.string().optional(),
@@ -381,10 +362,12 @@ strictTool("issue_list",
         // its own `.strict()`.
         .strict()
         .optional(),
-    fields: z
-        .array(z.enum(LIST_FIELD_GROUPS))
+    // DX-3427 — a field TREE, exactly like `issue_get`'s `fields` below
+    // (against the same shared issue resource) — replaces the retired
+    // CSV field-GROUP list.
+    fields: fieldTreeSchema
         .optional()
-        .describe("Field groups to add; absent = minimal scalars."),
+        .describe("A field tree (see tool description); absent/empty = minimal scalars. `resource_fields({resource:\"issue\"})` names every valid key."),
     sort: sortField,
     limit: z.number().int().positive().max(LIST_PAGE_MAX_LIMIT).optional(),
     offset: z.number().int().nonnegative().optional(),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@thehammer/danx-dashboard-mcp",
-  "version": "0.1.152",
+  "version": "0.1.154",
   "description": "Stdio MCP server wrapping danxbot's dashboard /api/issues/* normalized DB-backed HTTP routes for dispatched agents (DX-704 Phase 2).",
   "license": "MIT",
   "type": "module",