@aaronsb/jira-cloud-mcp 0.11.0 → 0.11.1

package/build/client/field-discovery.js

@@ -6,6 +6,7 @@
  * pass through unfiltered (no regression from pre-discovery behavior).
  */
 import { classifyFieldType } from './field-type-map.js';
+import { routeForField } from '../extensions/index.js';
 // ── Constants ──────────────────────────────────────────────────────────
 const HARD_CAP = 30;
 const SPREAD_RATIO_THRESHOLD = 10;
@@ -14,6 +15,18 @@ const SCREEN_WEIGHT = 10;
 const RECENCY_WEIGHT = 5;
 const RECENCY_HALF_LIFE_DAYS = 30;
 // ── Field Discovery ────────────────────────────────────────────────────
+/**
+ * True if an extension route owns a value-resolving write handler for this field (ADR-213 §B).
+ * Used to mark `writable: true` on a field whose Jira type our classifier can't map — e.g. Tempo
+ * Account reports an opaque schema (→ `unsupported` category) but `resolveTempoAccountWrite` turns
+ * a name into the numeric id the standard issue-edit endpoint accepts. Matches the route by field
+ * name first, then by schema-custom key. (#45 follow-up: keeps the catalog `writable` flag in
+ * step with what the write path actually does.)
+ */
+function extensionCanWrite(fieldName, schemaCustom) {
+    const route = routeForField(fieldName) ?? (schemaCustom ? routeForField(schemaCustom) : undefined);
+    return route?.resolveWrite != null;
+}
 /** Well-known locked fields identified by schema custom type */
 const WELL_KNOWN_FIELDS = {
     'com.pyxis.greenhopper.jira:gh-sprint': 'sprint',
@@ -427,7 +440,7 @@ export class FieldDiscovery {
                 name: f.name,
                 description: f.description,
                 category: typeInfo.category,
-                writable: typeInfo.writable,
+                writable: typeInfo.writable || extensionCanWrite(f.name, f.schemaCustom),
                 jsonSchema: typeInfo.jsonSchema,
                 schemaCustom: f.schemaCustom,
                 screensCount: 0,
@@ -473,6 +486,10 @@ export class FieldDiscovery {
                 continue;
             }
             // Filter: supported type
+            // NOTE: this also drops extension-handled fields whose Jira type our classifier can't map
+            // (e.g. Tempo Account on an admin tenant) — the unscored fallback keeps them and flags them
+            // writable via `extensionCanWrite`, but the scored path doesn't. Retaining them here is a
+            // larger change (it shifts what's in the curated catalog, not just a flag). See #45 / #57.
             const typeInfo = classifyFieldType(field.schemaType, field.schemaCustom || undefined, field.schemaItems || undefined);
             if (typeInfo.category === 'unsupported') {
                 excludedUnsupportedType++;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aaronsb/jira-cloud-mcp",
-  "version": "0.11.0",
+  "version": "0.11.1",
   "mcpName": "io.github.aaronsb/jira-cloud",
   "description": "Model Context Protocol (MCP) server for Jira Cloud - enables AI assistants to interact with Jira",
   "type": "module",