@ezmodo/mcp-server 0.14.4 → 0.18.0

package/tools/epics.js

@@ -3,7 +3,7 @@
  * MCP tools for managing epics
  *
  * Project-First Hierarchy: Epics belong to projects (required),
- * with optional component grouping and milestone linking. *
+ * with optional milestone linking. *
  * NAMING (E-107): an epic is not called "Epic" everywhere. A project's type
  * decides its vocabulary — a marketing project calls this a Campaign, a sales
  * project a Deal, a research project a Study. Read the words from
@@ -15,6 +15,28 @@
 import { LINKS_ARRAY_SCHEMA, RELATED_ITEM_SCHEMA } from './link-params.js';
 import { TASK_ITEM_PROPERTIES } from './task-item-schema.js';
 
+// A link staged on a plan or planned task before it exists (#2199, #2752).
+// Mirrors the desktop LinkDraft shape so a plan an AI saves back keeps the
+// links the desktop staged.
+const PLAN_LINKS_SCHEMA = {
+  type: 'array',
+  items: {
+    type: 'object',
+    properties: {
+      targetType: { type: 'string' },
+      targetId: { type: 'string' },
+      title: { type: 'string' },
+      source: { type: 'string', enum: ['deterministic', 'suggested', 'manual'] },
+      accepted: { type: 'boolean', description: 'false only for a suggestion that was turned down' },
+      rule: { type: 'string' },
+      confidence: { type: 'number' },
+      suggestionId: { type: 'string' },
+      matchedPaths: { type: 'array', items: { type: 'string' } },
+    },
+    required: ['targetType', 'targetId'],
+  },
+};
+
 export const EPIC_TOOLS = [
   {
     name: 'manage_epic',
@@ -126,11 +148,6 @@ export const EPIC_TOOLS = [
         },
         links: LINKS_ARRAY_SCHEMA,
         // --- Create-only: the epic's breakdown, created in the same request ---
-        componentId: {
-          type: 'string',
-          description: 'Component applied to every task in `tasks` that does not set its own ' +
-            '(create only). Get available components from get_current_project_context().',
-        },
         tasks: {
           type: 'array',
           description: 'Child tasks to create WITH the epic, in the same request (create only, 1-40). ' +
@@ -264,4 +281,139 @@ export const EPIC_TOOLS = [
       },
     },
   },
+  {
+    name: 'get_epic_plan',
+    description: 'Read an epic\'s plan (E-259): the planned tasks, notes, status, staged links and any ' +
+      'open planner questions, with ' +
+      '`currentRevision`, the version number you must send back to `update_epic_plan`. ' +
+      'Several people and their AIs can work on one plan, so read it right before you change it. ' +
+      'Pass `includeHistory` to see who changed what, in plain sentences, and `revision` to read an older version.',
+    inputSchema: {
+      type: 'object',
+      properties: {
+        epicId: { type: 'string', description: 'The epic ID (required)' },
+        revision: { type: 'number', description: 'Read this saved version instead of the current one' },
+        includeHistory: {
+          type: 'boolean',
+          description: 'Also return recent versions: who saved each, which AI, and what changed',
+        },
+        historyLimit: { type: 'number', description: 'How many versions of history to return (default 20)' },
+      },
+      required: ['epicId'],
+    },
+  },
+  {
+    name: 'update_epic_plan',
+    description: 'Save an epic\'s plan as a new version (E-259). Send the WHOLE plan, changed where you ' +
+      'mean to change it, plus `baseRevision`: the `currentRevision` you read with `get_epic_plan` ' +
+      '(0 when the epic has no plan). Keep each planned task\'s `id` so the change is matched to the right task. ' +
+      'If someone else saved since you read it, nothing is written and you get `PLAN_CONFLICT` with the ' +
+      'current plan and what changed — apply your change to THAT plan and save again with its revision. ' +
+      'Never resend your old copy: that erases their work. ' +
+      'Keep plans simple and readable by anyone: a plain title and one line on why for each task. ' +
+      'Only the epic\'s owner, its creator or an organization admin can save the plan; anyone else ' +
+      'suggests the change with add_epic_comment or asks it as a decision to make (manage_decision).',
+    inputSchema: {
+      type: 'object',
+      properties: {
+        epicId: { type: 'string', description: 'The epic ID (required)' },
+        baseRevision: {
+          type: 'number',
+          description: 'The currentRevision you started from (required; 0 for a new plan)',
+        },
+        plan: {
+          type: 'object',
+          description: 'The full plan. Fields not listed here (conversation, targetFeatureId, …) ' +
+            'are kept only if you send them back.',
+          properties: {
+            notes: { type: 'string', description: 'Assumptions, risks and scope notes' },
+            status: { type: 'string', enum: ['draft', 'approved'], description: 'draft (default) or approved' },
+            proposedTasks: {
+              type: 'array',
+              items: {
+                type: 'object',
+                properties: {
+                  id: { type: 'string', description: 'Keep the id from get_epic_plan; omit for a new task' },
+                  title: { type: 'string' },
+                  workType: { type: 'string' },
+                  description: { type: 'string' },
+                  steps: { type: 'array', items: { type: 'string' } },
+                  rationale: { type: 'string', description: 'One line on why this task exists' },
+                  dependsOnIndices: { type: 'array', items: { type: 'number' } },
+                  needsHumanGate: { type: 'boolean' },
+                  links: {
+                    ...PLAN_LINKS_SCHEMA,
+                    description: 'Links to create with this task when the plan is approved. Send back ' +
+                      'what get_epic_plan returned',
+                  },
+                },
+                required: ['title'],
+              },
+            },
+            links: {
+              ...PLAN_LINKS_SCHEMA,
+              description: 'Links for the epic, applied when the plan is approved. Send back what ' +
+                'get_epic_plan returned',
+            },
+            questions: {
+              type: 'array',
+              description: 'The planner\'s open clarifying questions, kept as returned by get_epic_plan. ' +
+                'A choice that needs several people\'s view belongs on the epic as a decision to make ' +
+                '(manage_decision with epicId) instead.',
+              items: {
+                type: 'object',
+                properties: {
+                  id: { type: 'string' },
+                  question: { type: 'string' },
+                  header: { type: 'string' },
+                  options: {
+                    type: 'array',
+                    items: {
+                      type: 'object',
+                      properties: { label: { type: 'string' }, description: { type: 'string' } },
+                      required: ['label'],
+                    },
+                  },
+                  multiSelect: { type: 'boolean' },
+                },
+                required: ['question'],
+              },
+            },
+          },
+        },
+      },
+      required: ['epicId', 'baseRevision', 'plan'],
+    },
+  },
+  {
+    name: 'list_epic_comments',
+    description: 'Read an epic\'s discussion (E-259), oldest first. Each comment says who wrote it and, ' +
+      'when an AI wrote it for them, which AI (`agentName`). Replies carry `parentId`. ' +
+      'Read this before planning or changing a shared epic: other people\'s questions and objections live here.',
+    inputSchema: {
+      type: 'object',
+      properties: {
+        epicId: { type: 'string', description: 'The epic ID (required)' },
+        limit: { type: 'number', description: 'Maximum comments to return (default 100, max 500)' },
+      },
+      required: ['epicId'],
+    },
+  },
+  {
+    name: 'add_epic_comment',
+    description: 'Post to an epic\'s discussion (E-259), or reply to a comment with `parentId`. ' +
+      'Posted as the person whose key you use, marked as written by you. ' +
+      'Mentioned people, the author you reply to and everyone following the epic are notified, ' +
+      'and posting makes that person follow it. Write plainly: one point per comment, readable by anyone.',
+    inputSchema: {
+      type: 'object',
+      properties: {
+        epicId: { type: 'string', description: 'The epic ID (required)' },
+        content: { type: 'string', description: 'The comment (markdown)' },
+        parentId: { type: 'string', description: 'Reply to this comment' },
+        mentions: { type: 'array', items: { type: 'string' }, description: 'User IDs to notify' },
+      },
+      required: ['epicId', 'content'],
+    },
+  },
 ];

package/tools/features.js

@@ -33,8 +33,13 @@ export const FEATURE_TOOLS = [
       properties: {
         action: {
           type: 'string',
-          enum: ['create', 'update', 'delete', 'link', 'unlink', 'promote_epic', 'generate_how_it_works', 'apply_how_it_works', 'apply_init'],
-          description: 'Action to perform. "promote_epic" creates a feature from an existing epic ' +
+          enum: [
+            'create', 'update', 'delete', 'link', 'unlink', 'paths',
+            'promote_epic', 'generate_how_it_works', 'apply_how_it_works', 'apply_init',
+          ],
+          description: 'Action to perform. "paths" adds, removes or replaces the code paths the ' +
+            'feature OWNS (featureId + paths + pathsMode) — work touching a file under an owned path ' +
+            'auto-links to the feature. "promote_epic" creates a feature from an existing epic ' +
             '(inheriting its title/description/scope) and links the epic to it. ' +
             '"generate_how_it_works" (re)generates the feature\'s grounded, source-attributed ' +
             '"how it works" living description from its linked work + code (requires featureId; ' +
@@ -116,6 +121,36 @@ export const FEATURE_TOOLS = [
           type: 'string',
           description: 'ID of the artifact to link/unlink (required for link, unlink)',
         },
+        // --- paths fields (E-258) ---
+        paths: {
+          type: 'array',
+          items: {
+            type: 'object',
+            properties: {
+              projectId: {
+                type: 'string',
+                description: 'Project the path lives in. Must be one the feature spans ' +
+                  '(any project in the org for an org-wide feature).',
+              },
+              sourcePath: {
+                type: 'string',
+                description: 'Repo-relative file or folder, e.g. "api/internal/core/features" or ' +
+                  '"web/src/app/checkout/page.tsx". Matched by exact prefix, NOT glob.',
+              },
+            },
+            required: ['projectId', 'sourcePath'],
+          },
+          description: 'Code paths for the "paths" action. A file resolves to the feature owning its ' +
+            'LONGEST matching folder or the exact file. Own what is characteristic of the capability; ' +
+            'leave shared plumbing (e.g. web/src/components/ui, api/internal/api/router.go) owned by no ' +
+            'feature — a path owned by several features only ever produces suggestions.',
+        },
+        pathsMode: {
+          type: 'string',
+          enum: ['add', 'remove', 'replace'],
+          description: 'How "paths" applies (default "add"). "replace" makes the list the feature\'s ' +
+            'entire path set; an empty list clears it.',
+        },
         // --- apply_init fields (E-167) ---
         nodes: {
           type: 'array',
@@ -164,6 +199,10 @@ export const FEATURE_TOOLS = [
           type: 'boolean',
           description: 'If true (single lookup), also return the feature\'s linked artifacts',
         },
+        includePaths: {
+          type: 'boolean',
+          description: 'If true (single lookup), also return the code paths the feature owns (E-258).',
+        },
         includeDetail: {
           type: 'boolean',
           description: 'If true (single lookup), return the aggregated detail: linked artifacts ' +

package/tools/git-context.js

@@ -33,13 +33,13 @@ export const GIT_CONTEXT_TOOLS = [
       'Returns project context if found, ' +
       'or null if not configured. Use this BEFORE other MCP tools to ' +
       'auto-detect which project you\'re working on. Project-First: ' +
-      'Returns projectId, components, and tags that can be used ' +
-      'directly with task/epic creation tools. Caches tags and ' +
-      'components locally with 1-day TTL for fast access. ' +
+      'Returns projectId and tags that can be used ' +
+      'directly with task/epic creation tools. Caches tags ' +
+      'locally with 1-day TTL for fast access. ' +
       'Also returns `projectType` and `terminology` — the words this project ' +
-      'uses for epics, tasks and components and for their statuses (E-107). ' +
+      'uses for epics and tasks and for their statuses (E-107). ' +
       'Write anything a person reads in those words: a marketing project calls ' +
-      'an epic a "Campaign" and a component a "Channel". Keep the API field ' +
+      'an epic a "Campaign". Keep the API field ' +
       'names (epicId, taskId) as they are. A null `terminology` means plain ' +
       'English, not an error.',
     inputSchema: {

package/tools/graph.js

@@ -4,7 +4,7 @@
  * The living navigation graph (E-209): a browsable, cross-entity projection
  * over the entity_links link graph (relates_to / blocked_by). One read lets an
  * agent walk "what connects to this" from any node — features, epics, tasks,
- * goals, milestones, components, designs, decisions, documents, test suites,
+ * goals, milestones, catalogs, designs, decisions, documents, test suites,
  * feature flags — instead of issuing N separate list_links calls and stitching
  * the results together.
  *

package/tools/index.js

@@ -10,13 +10,13 @@
 
 import { ORGANIZATION_TOOLS } from './organizations.js';
 import { PROJECT_TOOLS } from './projects.js';
-import { COMPONENT_TOOLS } from './components.js';
 import { EPIC_TOOLS } from './epics.js';
 import { MILESTONE_TOOLS } from './milestones.js';
 import { FEATURE_TOOLS } from './features.js';
 import { DECISION_TOOLS } from './decisions.js';
 import { DESIGN_TOOLS } from './designs.js';
 import { CATALOG_TOOLS } from './catalogs.js';
+import { UNMAPPED_PATH_TOOLS } from './unmapped-paths.js';
 import { FEATURE_FLAG_TOOLS } from './feature-flags.js';
 import { TASK_TOOLS } from './tasks.js';
 import { DOCUMENT_TOOLS } from './documents.js';
@@ -48,13 +48,13 @@ export const TOOLS = [
   ...AUTH_TOOLS,
   ...ORGANIZATION_TOOLS,
   ...PROJECT_TOOLS,
-  ...COMPONENT_TOOLS,
   ...EPIC_TOOLS,
   ...MILESTONE_TOOLS,
   ...FEATURE_TOOLS,
   ...DECISION_TOOLS,
   ...DESIGN_TOOLS,
   ...CATALOG_TOOLS,
+  ...UNMAPPED_PATH_TOOLS,
   ...FEATURE_FLAG_TOOLS,
   ...TASK_TOOLS,
   ...RECURRING_TASK_TOOLS,

package/tools/linkable-types.js

@@ -20,7 +20,6 @@ export const LINKABLE_TYPES = [
   'epic',
   'project',
   'document',
-  'component',
   'feature',
   'decision',
   'design',

package/tools/links.js

@@ -21,7 +21,7 @@ export const LINK_TOOLS = [
       'dependencies (blocked_by) and soft cross-entity links (relates_to) ' +
       'uniformly. blocked_by is only valid for task→task and epic→epic; ' +
       'relates_to works between any of: task, epic, project, document, ' +
-      'component, feature, decision, design, test_suite, feature_flag ' +
+      'feature, decision, design, test_suite, feature_flag, catalog, catalog_item ' +
       '(e.g. link a feature to the feature_flag that gates it). ' +
       'Idempotent — re-adding an existing link is a no-op, removing an ' +
       'absent link is a no-op. Use action "verify" to stamp a link\'s ' +
@@ -143,10 +143,13 @@ export const LINK_TOOLS = [
     name: 'resolve_links',
     description:
       'Given files you have touched (or are about to), return the entities you should link to: ' +
-      'the components — screens, pages, codebase areas — that own those paths, plus how confident ' +
-      'the match is. Read-only; nothing is written.\n\n' +
+      'the features (product capabilities) whose owned code paths cover them, plus how confident ' +
+      'each match is. Read-only; nothing is written.\n\n' +
+      '`features.owned` are capabilities that solely own a path: link them. `features.shared` are ' +
+      'paths several features claim: pick the one your work actually advanced. `unmatchedPaths` ' +
+      'are owned by no feature — a gap in the feature map, fixed with manage_feature action:"paths".\n\n' +
       'Call it BEFORE creating work to fill in the `links` param, or after a change set to check ' +
-      'you have not missed anything. If it returns a component you did not expect, that is a signal ' +
+      'you have not missed anything. If it returns a feature you did not expect, that is a signal ' +
       'your change is broader than you thought — worth reading before you continue.\n\n' +
       'Paths are repo-relative (e.g. "mobile/lib/features/auth/screens/login_screen.dart").',
     inputSchema: {
@@ -185,7 +188,6 @@ export const LINK_TOOLS = [
           items: { type: 'string' },
           description: 'Repo-relative file paths the work touches',
         },
-        componentId: { type: 'string', description: 'A component the work explicitly names' },
         epicId: { type: 'string', description: 'The epic the work belongs to' },
         trigger: {
           type: 'string',

package/tools/projects.js

@@ -7,7 +7,7 @@
  * creative, research, implementation, custom.
  *
  * A project's type decides what its work is CALLED (E-107). A marketing project
- * calls an epic a "Campaign" and a component a "Channel"; a sales project calls
+ * calls an epic a "Campaign"; a sales project calls
  * a task an "Activity". `get_project` returns the resolved vocabulary as
  * `terminology`, and `get_current_project_context` caches it. Use those words
  * when writing anything a person reads — titles, descriptions, chat replies —
@@ -106,7 +106,7 @@ export const PROJECT_TOOLS = [
       'Responses include `descriptionDocumentId` — the id of the backing rich-description Document ' +
       'when the description has been promoted to one (E-189), otherwise omitted. ' +
       'By-ID responses also carry `type` and `terminology` — the words this project uses for ' +
-      'epics, tasks and components, and for their statuses (E-107). Write prose in those words; ' +
+      'epics and tasks, and for their statuses (E-107). Write prose in those words; ' +
       'a marketing project calls an epic a "Campaign". `terminology` is absent for a type with no ' +
       'template, which means plain English, not an error.',
     inputSchema: {

package/tools/recurring-tasks.js

@@ -49,7 +49,6 @@ const INLINE_TASK_SCHEMA = {
     steps: { type: 'array', items: { type: 'string' } },
     priority: { type: 'string', enum: ['low', 'medium', 'high', 'urgent'] },
     taskType: TASK_TYPE_PROPERTY,
-    componentId: { type: 'string' },
     epicId: { type: 'string' },
     tagIds: { type: 'array', items: { type: 'string' } },
     assigneeId: { type: 'string' },

package/tools/task-item-schema.js

@@ -32,12 +32,6 @@ export const TASK_ITEM_PROPERTIES = {
     description: 'Initial status (defaults to todo)',
   },
   taskType: TASK_TYPE_PROPERTY,
-  componentId: { type: 'string', description: 'DEPRECATED single component; overrides the shared componentId. Prefer componentIds.' },
-  componentIds: {
-    type: 'array',
-    items: { type: 'string' },
-    description: 'Every component this task touches; overrides the shared componentId/componentIds.',
-  },
   parentTaskId: { type: 'string', description: 'Parent task link' },
   estimatedHours: { type: 'number' },
   assigneeType: { type: 'string', enum: ['human', 'ai'] },

package/tools/tasks.js

@@ -3,7 +3,8 @@
  * MCP tools for managing tasks
  *
  * Project-First Hierarchy: Tasks belong to projects (required), with optional
- * component and epic grouping.
+ * epic grouping. Code links are derived from the files a task touches, which
+ * resolve to the features that own them (E-258).
  *
  * NAMING (E-107): a project's type renames a task and its statuses — a sales
  * project calls a task an "Activity" and calls `in_review` "Awaiting Approval".
@@ -24,7 +25,8 @@ export const TASK_TOOLS = [
       'to discover relevant files, patterns, and dependencies. (2) Write descriptions that explain WHY ' +
       '(problem/goal), WHERE (specific files/endpoints from context), and HOW (approach using existing patterns). ' +
       '(3) Write steps that reference specific file paths, not vague instructions. ' +
-      '(4) Every task should name the components it touches via componentIds — use get_current_project_context() to get available components.',
+      '(4) Link the feature the work advances with links:[{targetType:"feature", targetId}] (find it with ' +
+      'search_features), and pass changedFiles — the files resolve to the features that own those paths.',
     inputSchema: {
       type: 'object',
       properties: {
@@ -68,16 +70,6 @@ export const TASK_TOOLS = [
           description: 'Task description (supports markdown). Use real newlines, not literal \\n. Used by create and update. ' +
             'Writing this stays plain text; it does not create a backing document.',
         },
-        componentId: {
-          type: 'string',
-          description: 'DEPRECATED single component. Still accepted \u2014 it is treated as a one-element componentIds \u2014 but prefer componentIds: a task touches every component its work spans, and this field can only name one of them.',
-        },
-        componentIds: {
-          type: 'array',
-          items: { type: 'string' },
-          description: 'Every component this task touches. Get available components from get_current_project_context(). ' +
-            'On update this REPLACES the set: pass the full list, and an empty array clears it. Wins over componentId when both are given.',
-        },
         epicId: {
           type: 'string',
           description: 'Epic ID to link this task to. Used by create and update (set to empty string to remove on update).',
@@ -212,8 +204,9 @@ export const TASK_TOOLS = [
           items: { type: 'string' },
           description:
             'Repo-relative paths you touched. Simpler alternative to linkedFiles — just the paths. ' +
-            'ezmodo resolves them to the components (screens/pages/areas) that own them and links ' +
-            'this task to them automatically; anything it is unsure about comes back as ' +
+            'ezmodo resolves them to the features that own those paths and links this task to them ' +
+            'automatically; a path several features share comes back as a suggestion, as does anything ' +
+            'else it is unsure about, in ' +
             'linkSuggestions for you to accept or reject. Used by create and update.',
         },
         autolink: {
@@ -458,7 +451,7 @@ export const TASK_TOOLS = [
       'the authentication, plan check, rate-limit accounting and database connection ' +
       'setup once instead of per task; a burst of individual creates is what made the ' +
       'app unresponsive for 45 minutes on 2026-07-28. ' +
-      'Put shared values (projectId, epicId, componentIds) at the TOP LEVEL and let the ' +
+      'Put shared values (projectId, epicId) at the TOP LEVEL and let the ' +
       'items inherit them — only override per item where a task genuinely differs. ' +
       'Each item accepts the same fields as manage_task action:"create". ' +
       'Returns a per-item result array: on partial failure retry ONLY the items marked ' +
@@ -480,18 +473,6 @@ export const TASK_TOOLS = [
           description: 'Epic applied to every item that does not set its own. The ' +
             'usual case for a breakdown: one epic for the whole batch.',
         },
-        componentId: {
-          type: 'string',
-          description: 'DEPRECATED single component applied to every item that does ' +
-            'not name its own. Prefer componentIds.',
-        },
-        componentIds: {
-          type: 'array',
-          items: { type: 'string' },
-          description: 'Components applied to every item that does not name its own. ' +
-            'An item naming either form keeps its own set. ' +
-            'Get available components from get_current_project_context().',
-        },
         tasks: {
           type: 'array',
           description: 'The tasks to create (1-40). Each item takes the same fields ' +
@@ -515,7 +496,7 @@ export const TASK_TOOLS = [
   {
     name: 'search_tasks',
     description: 'Search for tasks with filters or semantic search. ' +
-      'Use for filtered queries (by status, priority, component, etc). ' +
+      'Use for filtered queries (by status, priority, epic, etc). ' +
       'To get ALL tasks in an epic, prefer get_epic with includeTasks=true. ' +
       'Use search_tasks with epicId only when you need additional filtering ' +
       '(e.g., only in_progress tasks within an epic). ' +
@@ -528,10 +509,6 @@ export const TASK_TOOLS = [
           type: 'string',
           description: 'Filter by project ID (primary scope)',
         },
-        componentId: {
-          type: 'string',
-          description: 'Filter by component ID (codebase area)',
-        },
         epicId: {
           type: 'string',
           description: 'Filter by epic ID (feature grouping)',
@@ -620,18 +597,6 @@ export const TASK_TOOLS = [
           description: 'Repo-relative paths of files that were changed. Recorded in the ' +
             'description and linked to the task for dependency inference.',
         },
-        componentId: {
-          type: 'string',
-          description: 'DEPRECATED single component. Still accepted as a one-element ' +
-            'componentIds, but prefer componentIds \u2014 untracked work often spans ' +
-            'more than one area, which is part of why it was untracked.',
-        },
-        componentIds: {
-          type: 'array',
-          items: { type: 'string' },
-          description: 'Every component this work touched. Get available components ' +
-            'from get_current_project_context().',
-        },
         epicId: {
           type: 'string',
           description: 'Epic this work belongs under. Set it when the untracked work ' +

package/tools/todos.js

@@ -44,10 +44,6 @@ export const TODO_TOOLS = [
           type: 'string',
           description: 'Optional epic to assign the task to (move_to_project only)',
         },
-        componentId: {
-          type: 'string',
-          description: 'Optional component to assign the task to (move_to_project only)',
-        },
       },
       required: ['action'],
     },

package/tools/unmapped-paths.js

@@ -0,0 +1,72 @@
+/**
+ * Unmapped code path tools (E-258 #2756)
+ *
+ * When Components were retired, every component source path that belonged to no
+ * feature was recorded for review instead of being dropped. Each row is one
+ * question — "which capability owns this code?" — and until it is answered, work
+ * touching those files auto-links to nothing.
+ *
+ * The list lived only on the project Features page, so an agent asked to tidy it
+ * could set feature paths but never see or close the rows. These two tools make
+ * that loop completable.
+ */
+
+export const UNMAPPED_PATH_TOOLS = [
+  {
+    name: 'list_unmapped_paths',
+    description: 'List a project\'s unmapped code paths — former component paths that no feature owns ' +
+      '(E-258). Each row carries the source path and the component it came from. A pending row means ' +
+      'work touching those files links to no capability, so this is the backlog to work through when ' +
+      'a project\'s features are missing code ownership.',
+    inputSchema: {
+      type: 'object',
+      properties: {
+        projectId: {
+          type: 'string',
+          description: 'Project ID (required)',
+        },
+        status: {
+          type: 'string',
+          enum: ['pending', 'assigned', 'dismissed', 'all'],
+          description: 'Which rows to return (default "pending")',
+        },
+      },
+      required: ['projectId'],
+    },
+  },
+  {
+    name: 'resolve_unmapped',
+    description: 'Resolve unmapped code paths (E-258). "reconcile" is the one to reach for first: it ' +
+      'closes every pending row a feature has SINCE been given a path for, so the usual flow is to set ' +
+      'ownership with manage_feature action:"paths" and then reconcile, rather than answering rows one ' +
+      'by one. A path several features own stays pending — shared ownership is a judgement, and those ' +
+      'only ever produce link suggestions anyway.\n\n' +
+      '"assign" gives ONE row to a feature (adding that feature path, with the usual scope check), and ' +
+      '"dismiss" records that the path belongs to no capability — the right answer for shared plumbing.',
+    inputSchema: {
+      type: 'object',
+      properties: {
+        action: {
+          type: 'string',
+          enum: ['reconcile', 'assign', 'dismiss'],
+          description: 'reconcile: close every pending row an existing feature path already covers. ' +
+            'assign: give one row (pathId) to featureId. dismiss: mark one row (pathId) as owned by nobody.',
+        },
+        projectId: {
+          type: 'string',
+          description: 'Project ID (required for every action)',
+        },
+        pathId: {
+          type: 'string',
+          description: 'Unmapped path ID, from list_unmapped_paths (required for assign and dismiss)',
+        },
+        featureId: {
+          type: 'string',
+          description: 'Feature to give the path to (required for assign). It must span the project, ' +
+            'or be org-wide.',
+        },
+      },
+      required: ['action', 'projectId'],
+    },
+  },
+];

package/tools/work-templates.js

@@ -20,7 +20,6 @@ const TASK_BLUEPRINT_SCHEMA = {
     steps: { type: 'array', items: { type: 'string' } },
     taskType: TASK_TYPE_PROPERTY,
     priority: { type: 'string', enum: ['low', 'medium', 'high', 'urgent'] },
-    componentId: { type: 'string' },
     tagIds: { type: 'array', items: { type: 'string' } },
   },
   required: ['title'],
@@ -79,7 +78,6 @@ export const WORK_TEMPLATE_TOOLS = [
         title: { type: 'string', description: 'Instantiate: override the blueprint title.' },
         epicId: { type: 'string', description: 'Instantiate (task kind): attach the new task to this epic.' },
         milestoneId: { type: 'string', description: 'Instantiate (epic kind): link the new epic to this milestone.' },
-        componentId: { type: 'string', description: 'Instantiate (task kind): override component.' },
         priority: {
           type: 'string',
           enum: ['low', 'medium', 'high', 'urgent'],