@thehammer/danx-dashboard-mcp 0.1.152 → 0.1.156

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);
@@ -124,47 +126,11 @@ export async function issueGet(client, args) {
         board: args.board,
     });
 }
-// ---------------- repo_knowledge_get / repo_knowledge_set ----------------
-const REPO_KNOWLEDGE_BASE_PATH = "/api/repo-knowledge";
-/**
- * Fetch the board's working-knowledge doc via GET /api/repo-knowledge
- * (DX-1128, Story 2). Mirrors `issueGet` — a bare board-scoped GET, no id
- * (the doc is 1-per-board). Board resolves the same way every other tool's
- * `board` arg does: per-call override, else the dispatch's env-derived board.
- */
-export async function repoKnowledgeGet(client, args = {}) {
-    return client.request({
-        method: "GET",
-        path: "",
-        basePath: REPO_KNOWLEDGE_BASE_PATH,
-        board: args.board,
-    });
-}
-/**
- * Write the board's working-knowledge doc via PUT /api/repo-knowledge
- * (DX-1128, Story 2). Mirrors `issueEdit`'s shape (a PATCH-like body write)
- * but targets the repo-knowledge route family, not `/api/issues`. The
- * server's optimistic-concurrency guard rejects a stale `base_hash` — the
- * refusal envelope (`{ok: false, body: {error, currentHash}}`) passes
- * through verbatim so the caller can re-get, re-merge, and retry.
- */
-export async function repoKnowledgeSet(client, args) {
-    const { board, ...body } = args;
-    return client.request({
-        method: "PUT",
-        path: "",
-        basePath: REPO_KNOWLEDGE_BASE_PATH,
-        body,
-        board,
-    });
-}
 // ---------------- brief_list / brief_get_page / brief_set_page ----------------
 const BRIEF_BASE_PATH = "/api/brief";
 /**
  * List the board's named Brief pages via GET /api/brief (DX-2083).
- * Mirrors `repoKnowledgeGet`'s shape (a bare board-scoped GET, no id) but
- * targets the list-shaped sibling surface — many named pages per board,
- * not one document.
+ * A bare board-scoped GET, no id — many named pages per board.
  */
 export async function briefList(client, args = {}) {
     return client.request({
@@ -177,7 +143,7 @@ export async function briefList(client, args = {}) {
 /**
  * Fetch one Brief page by slug via GET /api/brief/page?slug=
  * (DX-2083). A missing row (including a not-yet-created page) reads as the
- * same empty-view convention `repoKnowledgeGet` uses — never a 404.
+ * empty view — never a 404.
  */
 export async function briefGetPage(client, args) {
     return client.request({
@@ -190,10 +156,9 @@ export async function briefGetPage(client, args) {
 }
 /**
  * Write one Brief page via PUT /api/brief/page?slug= (DX-2083).
- * Mirrors `repoKnowledgeSet`'s shape (optimistic-concurrency `base_hash`,
- * verbatim 409 passthrough on a stale write) but targets one named page
- * instead of the board's single working-knowledge doc. `slug` rides the
- * query string (matching the route), never the body.
+ * Optimistic-concurrency `base_hash` with a verbatim 409 passthrough on a
+ * stale write. `slug` rides the query string (matching the route), never
+ * the body.
  */
 export async function briefSetPage(client, args) {
     const { slug, board, ...body } = args;

package/dist/index.js

@@ -34,8 +34,6 @@
  *   - issue_attach           POST   /api/issues/:id/attachments (reads a local file)
  *   - quality_gate_instruction
  *                            GET    /api/quality-gates/:gate/instruction (DX-3341, not card-scoped)
- *   - repo_knowledge_get     GET    /api/repo-knowledge
- *   - repo_knowledge_set     PUT    /api/repo-knowledge (DX-1128, Story 2)
  *   - brief_list       GET    /api/brief
  *   - brief_get_page   GET    /api/brief/page (DX-2083 / DX-2484)
  *   - brief_set_page   PUT    /api/brief/page (DX-2083 / DX-2484)
@@ -110,7 +108,7 @@ import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
 import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
 import { z } from "zod";
 import { DashboardHttpClient } from "./http-client.js";
-import { issueAttach, issueChecklist, issueComment, issueCreate, issueDependency, issueEdit, issueGet, issueList, issueProblem, issueQualityGate, issueQualityGateVerdict, issueRetireBranch, issueRetro, issueSolution, issueTransition, issueTriage, briefGetPage, briefList, briefSetPage, failureCategoryCreate, failureCategoryList, failureCategoryUpdate, dispatchTranscriptSearch, planAddArchitectureSection, planAddCard, planAddNote, planAddRecord, planConnect, planCreate, planDeleteArchitectureSection, planDeleteNote, planDeleteRecord, planGet, PLAN_FIELD_GROUPS, PLAN_EVENT_KINDS, PLAN_EVENT_ORIGINS, PLAN_STATUSES, ISSUE_BATCH_GET_MAX, LIST_PAGE_MAX_LIMIT, PLAN_GET_CARDS_DEFAULT_LIMIT, PLAN_GET_EVENTS_DEFAULT_LIMIT, PLAN_GET_EVENTS_MAX_LIMIT, planGetArchitectureSection, planGetRecord, planList, planRemoveCard, planRename, planReorderArchitectureSection, planUpdateArchitectureSection, planUpdateNote, planUpdateRecord, repoKnowledgeGet, repoKnowledgeSet, qualityGateInstruction, resourceFields, } from "./handlers.js";
+import { issueAttach, issueChecklist, issueComment, issueCreate, issueDependency, issueEdit, issueGet, issueList, issueProblem, issueQualityGate, issueQualityGateVerdict, issueRetireBranch, issueRetro, issueSolution, issueTransition, issueTriage, briefGetPage, briefList, briefSetPage, failureCategoryCreate, failureCategoryList, failureCategoryUpdate, dispatchTranscriptSearch, planAddArchitectureSection, planAddCard, planAddNote, planAddRecord, planConnect, planCreate, planDeleteArchitectureSection, planDeleteNote, planDeleteRecord, planGet, PLAN_FIELD_GROUPS, PLAN_EVENT_KINDS, PLAN_EVENT_ORIGINS, PLAN_STATUSES, ISSUE_BATCH_GET_MAX, LIST_PAGE_MAX_LIMIT, PLAN_GET_CARDS_DEFAULT_LIMIT, PLAN_GET_EVENTS_DEFAULT_LIMIT, PLAN_GET_EVENTS_MAX_LIMIT, planGetArchitectureSection, planGetRecord, planList, planRemoveCard, planRename, planReorderArchitectureSection, planUpdateArchitectureSection, planUpdateNote, planUpdateRecord, qualityGateInstruction, resourceFields, } from "./handlers.js";
 import { PRIORITY_TIER_WORDS } from "./priority.js";
 import { fieldTreeSchema } from "./field-tree.js";
 function readEnvOrDie(name) {
@@ -277,25 +275,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 +339,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 +360,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(),
@@ -891,21 +872,8 @@ strictTool("issue_attach", "Attach a LOCAL file to an issue card: `id` (the card
         .describe("Absolute path to a local file on the dispatch's shared filesystem (must start with `/`)."),
     ...boardField,
 }, async (args) => jsonResult(await issueAttach(client, args)));
-// ---------------- repo_knowledge_get ----------------
-strictTool("repo_knowledge_get", "Fetch the board's working-knowledge markdown doc. Board-scoped; see `board`. Returns `{ok, status, body: {content, contentHash, updatedAt, updatedBy, boardId}}` — an unset doc reads as the empty view (content/contentHash `\"\"`), not a 404. Before `repo_knowledge_set`, always get immediately first and pass `contentHash` back as `base_hash` — the concurrency guard rejects a stale write.", {
-    ...boardField,
-}, async (args) => jsonResult(await repoKnowledgeGet(client, args)));
-// ---------------- repo_knowledge_set ----------------
-strictTool("repo_knowledge_set", 'Write the board\'s working-knowledge markdown doc. Board-scoped; see `board`. `base_hash` must be the `contentHash` from the immediately-prior `repo_knowledge_get` ("" for the true first write). On mismatch, fails loud with `{error: "stale_repo_knowledge", currentHash}` rather than overwriting — re-get, re-merge, retry with the new hash. On success persists to the DB, publishes `repo-knowledge:updated` over SSE, and returns the new view.', {
-    content: z.string(),
-    base_hash: z
-        .string()
-        .optional()
-        .describe('The contentHash last read via repo_knowledge_get ("" for a true first write). Omitted also normalizes to "" server-side, so it only succeeds against an empty/absent doc — always get immediately before set.'),
-    ...boardField,
-}, async (args) => jsonResult(await repoKnowledgeSet(client, args)));
 // ---------------- brief_list ----------------
-strictTool("brief_list", "List the board's named Brief pages. Board-scoped; see `board`. Returns `{boardId, pages: [{slug, title, contentHash, sortOrder, updatedAt, updatedBy}]}` — metadata only, no content (use `brief_get_page`). Unlike `repo_knowledge_get`/`_set` (one board-level doc), Brief pages are MANY named pages per board (Goals/Architecture/Rules/Caveats tabs), keyed by (board, slug). The reserved `index` slug always exists.", {
+strictTool("brief_list", "List the board's named Brief pages. Board-scoped; see `board`. Returns `{boardId, pages: [{slug, title, contentHash, sortOrder, updatedAt, updatedBy}]}` — metadata only, no content (use `brief_get_page`). Brief pages are MANY named pages per board (Goals/Architecture/Rules/Caveats tabs), keyed by (board, slug). The reserved `index` slug always exists.", {
     ...boardField,
 }, async (args) => jsonResult(await briefList(client, args)));
 // ---------------- brief_get_page ----------------
@@ -917,7 +885,7 @@ strictTool("brief_get_page", 'Fetch one Brief page by slug. Board-scoped; see `b
     ...boardField,
 }, async (args) => jsonResult(await briefGetPage(client, args)));
 // ---------------- brief_set_page ----------------
-strictTool("brief_set_page", 'Write one Brief page. Board-scoped; see `board`. Body: `{content, title?, sortOrder?, base_hash?}` — same optimistic-concurrency shape as `repo_knowledge_set`, targeting one named page. `base_hash` must be the `contentHash` from the immediately-prior `brief_get_page` (`""` for a true first write). On mismatch fails loud with `{error: "stale_brief_page", currentHash}` — re-get, re-merge, retry, never overwrite blindly. On success persists, publishes `brief:updated` over SSE, and returns the new view. No delete tool on this surface; the reserved `index` slug is never deletable — removing a non-index page is dashboard-UI-only.', {
+strictTool("brief_set_page", 'Write one Brief page. Board-scoped; see `board`. Body: `{content, title?, sortOrder?, base_hash?}` — optimistic-concurrency, targeting one named page. `base_hash` must be the `contentHash` from the immediately-prior `brief_get_page` (`""` for a true first write). On mismatch fails loud with `{error: "stale_brief_page", currentHash}` — re-get, re-merge, retry, never overwrite blindly. On success persists, publishes `brief:updated` over SSE, and returns the new view. No delete tool on this surface; the reserved `index` slug is never deletable — removing a non-index page is dashboard-UI-only.', {
     slug: z
         .string()
         .min(1)

package/package.json

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