@ezmodo/mcp-server 0.14.4 → 0.17.1

package/lib/local-cache.js

@@ -1,6 +1,6 @@
 /**
  * Local Cache Utility
- * Reads and writes the project config.json cache for tags and components.
+ * Reads and writes the project config.json cache for tags.
  * Looks in `.ezmodo/` first, falls back to legacy `.zephly/`.
  * Used by MCP handlers to avoid unnecessary API calls for frequently-read data.
  */
@@ -94,23 +94,9 @@ export async function getCachedTags() {
   return config.tags || null;
 }
 
-/**
- * Get cached components for a specific project if the cache is fresh.
- * @param {string} projectId - Only return components if they match this project
- * @returns {Promise<Array|null>} Cached components array, or null if stale/missing/wrong project
- */
-export async function getCachedComponents(projectId) {
-  const config = await readConfig();
-  if (!config) return null;
-  if (!isCacheFresh(config.lastUpdatedAt)) return null;
-  // Only return if the cached config belongs to this project
-  if (config.projectId !== projectId) return null;
-  return config.components || null;
-}
-
 /**
  * Update specific sections in the config cache. Non-fatal on failure.
- * @param {object} updates - Key-value pairs to merge into config (e.g., { tags: [...], components: [...] })
+ * @param {object} updates - Key-value pairs to merge into config (e.g., { tags: [...] })
  */
 export async function updateCacheSections(updates) {
   try {
@@ -126,7 +112,7 @@ export async function updateCacheSections(updates) {
 /**
  * Invalidate a specific cache section by removing it from config.
  * The next read will return null, triggering a fresh API call.
- * @param {string} section - 'tags' or 'components'
+ * @param {string} section - e.g. 'tags'
  */
 export async function invalidateCacheSection(section) {
   try {

package/lib/remote-tools.js

@@ -93,7 +93,6 @@ export const REMOTE_SAFE_TOOLS = Object.freeze([
   'list_attachments',
   'list_catalog_items',
   'list_catalogs',
-  'list_components',
   'list_designs',
   'list_epics',
   'list_facts',
@@ -110,7 +109,6 @@ export const REMOTE_SAFE_TOOLS = Object.freeze([
   'list_watched',
   'manage_access',
   'manage_catalog',
-  'manage_component',
   'manage_decision',
   'manage_design',
   'manage_document',

package/lib/version.js

@@ -7,4 +7,4 @@
  *
  * Update this when bumping the version in package.json.
  */
-export const MCP_VERSION = '0.14.4';
+export const MCP_VERSION = '0.17.1';

package/package.json

@@ -1,14 +1,14 @@
 {
   "name": "@ezmodo/mcp-server",
-  "version": "0.14.4",
+  "version": "0.17.1",
   "description": "MCP server for ezmodo - AI-first project management",
   "main": "index.js",
   "type": "module",
   "bin": {
-    "mcp-server": "./index.js",
-    "ezmodo-mcp-server": "./index.js",
-    "zephly-mcp-server": "./index.js",
-    "ezmodo-mcp-server-http": "./http.js"
+    "mcp-server": "index.js",
+    "ezmodo-mcp-server": "index.js",
+    "zephly-mcp-server": "index.js",
+    "ezmodo-mcp-server-http": "http.js"
   },
   "scripts": {
     "dev": "BUILD_ENV=development node index.js",

package/prompts/commands.generated.js

@@ -18,7 +18,7 @@ export const COMMAND_PROMPTS = [
       "local",
       "remote"
     ],
-    "body": "Start tracked work on: **$ARGUMENTS**\n\nFollow the work-tracking contract in this server's instructions. In short:\n\n1. `get_current_project_context()` — cache the `projectId`, note the components,\n   tags and `terminology`.\n2. `get_context` with a keyword query drawn from the request above. Read what\n   comes back before writing anything: it tells you which files exist, what\n   patterns they follow, and what the change will touch.\n3. `resolve_links` on the paths you expect to change. A component you did not\n   expect means the work is broader than the request sounds.\n4. Create the work:\n   - **Single scope** (a fix, a small feature, a config or docs change) —\n     `manage_task action:\"create\"` with `status:\"in_progress\"`, a description\n     that says why/where/how, steps that name real files, `componentIds` for\n     every component involved, and the right `taskType`.\n   - **Multi scope** (spanning areas, or a large refactor) — `manage_epic\n     action:\"create\"` with its child tasks in the same request, ordered by\n     dependency.\n\nThen report the task number and web URL and begin. Do not edit anything before\nthe task exists — a task created afterwards is a task written from memory.\n\nIf no `.ezmodo/config.json` is found, say so and stop rather than guessing at a\nproject."
+    "body": "Start tracked work on: **$ARGUMENTS**\n\nFollow the work-tracking contract in this server's instructions. In short:\n\n1. `get_current_project_context()` — cache the `projectId`, note the tags and\n   `terminology`.\n2. `get_context` with a keyword query drawn from the request above. Read what\n   comes back before writing anything: it tells you which files exist, what\n   patterns they follow, and what the change will touch.\n3. `resolve_links` on the paths you expect to change. A feature you did not\n   expect means the work is broader than the request sounds.\n4. Create the work:\n   - **Single scope** (a fix, a small feature, a config or docs change) —\n     `manage_task action:\"create\"` with `status:\"in_progress\"`, a description\n     that says why/where/how, steps that name real files, `changedFiles` for\n     the paths involved, a `links` entry for the feature it advances, and the\n     right `taskType`.\n   - **Multi scope** (spanning several parts of the codebase, or a large refactor) — `manage_epic\n     action:\"create\"` with its child tasks in the same request, ordered by\n     dependency.\n\nThen report the task number and web URL and begin. Do not edit anything before\nthe task exists — a task created afterwards is a task written from memory.\n\nIf no `.ezmodo/config.json` is found, say so and stop rather than guessing at a\nproject."
   },
   {
     "name": "resume",
@@ -47,6 +47,6 @@ export const COMMAND_PROMPTS = [
       "local",
       "remote"
     ],
-    "body": "Capture the current uncommitted work as a task.\n\nCurrent branch: run `git rev-parse --abbrev-ref HEAD` and use its output\nChanged files: run `git status --porcelain` and use its output\n\nUse `report_untracked_work` with:\n\n- `projectId` from `get_current_project_context()`\n- `title` — concise, describing what was actually done\n- `description` — what and **why**. Do not restate the branch or file list; they\n  are appended automatically as evidence.\n- `changedFiles` — the paths above\n- `branch` — as above\n- `componentIds` — resolve the changed paths with `resolve_links` rather than\n  guessing; untracked work often spans more than one area, which is part of why\n  it went untracked\n- `origin`:\n  - `discovered` — found while working on another task (set `discoveredDuringTaskId`)\n  - `scope-creep` — went beyond the active task's scope (set `discoveredDuringTaskId`)\n  - `rework` — redoing prior work\n  - `untracked` — unplanned standalone work (the default)\n\nIf there is an active task in this session, prefer `discovered` or\n`scope-creep` and link it — the discovery chain is the point of the\nclassification.\n\nThe new task comes back `in_progress` and becomes the active one. Track against\nit for the rest of the work.\n\nExtra context from the user, if any: $ARGUMENTS"
+    "body": "Capture the current uncommitted work as a task.\n\nCurrent branch: run `git rev-parse --abbrev-ref HEAD` and use its output\nChanged files: run `git status --porcelain` and use its output\n\nUse `report_untracked_work` with:\n\n- `projectId` from `get_current_project_context()`\n- `title` — concise, describing what was actually done\n- `description` — what and **why**. Do not restate the branch or file list; they\n  are appended automatically as evidence.\n- `changedFiles` — the paths above\n- `branch` — as above\n- `origin`:\n  - `discovered` — found while working on another task (set `discoveredDuringTaskId`)\n  - `scope-creep` — went beyond the active task's scope (set `discoveredDuringTaskId`)\n  - `rework` — redoing prior work\n  - `untracked` — unplanned standalone work (the default)\n\nIf there is an active task in this session, prefer `discovered` or\n`scope-creep` and link it — the discovery chain is the point of the\nclassification.\n\nThe new task comes back `in_progress` and becomes the active one. Track against\nit for the rest of the work.\n\nExtra context from the user, if any: $ARGUMENTS"
   }
 ];

package/tools/catalogs.js

@@ -80,8 +80,14 @@ export const CATALOG_TOOLS = [
     name: 'manage_catalog',
     description: 'Create, update, or delete an org-level Catalog, link/unlink it to other artifacts, ' +
       'or push a new versioned snapshot of its contents. A Catalog is a generalized, code-derived ' +
-      'catalog (kind = notifications | analytics_events | db_schema | custom); its versions are ' +
+      'catalog (kind = notifications | analytics_events | db_schema | screens | custom); its versions are ' +
       'immutable { columns, items } snapshots.\n\n' +
+      'SCREENS (E-258): each project has one kind:"screens" catalog, its UI inventory (screens and pages, ' +
+      'keyed by source path). Do not snapshot it by hand: action:"discover_screens" (projectId) lists what ' +
+      'the Context Manifest shows that the catalog lacks, and action:"import_screens" (projectId, screens, ' +
+      'optional featureId) adds them and links each to the feature. action:"sync_screens" (projectId) ' +
+      'reconciles the catalog with the manifest and re-derives the screen flow map (navigates_to edges ' +
+      'between screens); it cannot remove a hand-added screen or a human-confirmed edge.\n\n' +
       'CAPTURE-AT-BUILD (important): whenever you change the catalog\'s source of truth in code, call ' +
       'action:"snapshot" and put the source path/commit in `source`. The server is checksum-gated — ' +
       're-snapshotting unchanged content creates no new version and is a cheap no-op — so it is safe ' +
@@ -97,7 +103,7 @@ export const CATALOG_TOOLS = [
       '`go run ./cmd/dbschema-snapshot -upload -catalog-id <id>` from api/ introspects and uploads the ' +
       'whole schema without passing it through the model at all — cheaper still than a patch.\n\n' +
       'LINK, DON\'T CONTAIN: use action:"link"/"unlink" to relate a catalog to a feature, feature_flag, ' +
-      'epic, task, document, component, milestone, goal or project (e.g. link the notification catalog ' +
+      'epic, task, document, milestone, goal or project (e.g. link the notification catalog ' +
       'to its Notifications feature and the ezmodo doc that describes it).\n\n' +
       'ITEM-LEVEL LINKS (E-218): pass `itemKey` on action:"link"/"unlink" to attach the link to a SINGLE ' +
       'catalog entry instead of the whole catalog — this is how a task/epic that builds one entry records ' +
@@ -109,7 +115,8 @@ export const CATALOG_TOOLS = [
       properties: {
         action: {
           type: 'string',
-          enum: ['create', 'update', 'delete', 'link', 'unlink', 'snapshot'],
+          enum: ['create', 'update', 'delete', 'link', 'unlink', 'snapshot', 'discover_screens', 'import_screens',
+            'sync_screens'],
           description: 'Action to perform. "snapshot" pushes a new version (checksum-gated) — send a ' +
             'delta with mode:"patch" unless this is the catalog\'s first snapshot. "link"/"unlink" ' +
             'manage relates_to edges to other artifacts.',
@@ -127,10 +134,30 @@ export const CATALOG_TOOLS = [
           type: 'string',
           description: 'Catalog ID (required for update, delete, link, unlink, snapshot)',
         },
+        // --- Screens (E-258) ---
+        screens: {
+          type: 'array',
+          description: 'Screens to add for import_screens, usually taken from discover_screens.',
+          items: {
+            type: 'object',
+            properties: {
+              name: { type: 'string', description: 'Display name, e.g. "CookSessionDetailScreen"' },
+              sourcePath: { type: 'string', description: 'Repo-relative file; becomes the item key' },
+              kind: { type: 'string', enum: ['screen', 'page'], description: 'Default "screen"' },
+              route: { type: 'string', description: 'Route, for web pages' },
+              framework: { type: 'string', description: 'e.g. "nextjs", "flutter"' },
+            },
+            required: ['name', 'sourcePath'],
+          },
+        },
+        featureId: {
+          type: 'string',
+          description: 'Feature to link every imported screen to (import_screens)',
+        },
         // --- Create / update fields ---
         kind: {
           type: 'string',
-          enum: ['db_schema', 'notifications', 'analytics_events', 'custom'],
+          enum: ['db_schema', 'notifications', 'analytics_events', 'screens', 'custom'],
           description: 'What the catalog catalogs (default "custom") (create, update)',
         },
         name: {
@@ -276,7 +303,7 @@ export const CATALOG_TOOLS = [
         },
         kind: {
           type: 'string',
-          enum: ['db_schema', 'notifications', 'analytics_events', 'custom'],
+          enum: ['db_schema', 'notifications', 'analytics_events', 'screens', 'custom'],
           description: 'Filter to a single kind',
         },
         linkedType: {

package/tools/context-manifest.js

@@ -13,7 +13,7 @@ export const CONTEXT_MANIFEST_TOOLS = [
   {
     name: 'get_context',
     description:
-      'Get contextual information about any entity (project, task, epic, component, file, tag). ' +
+      'Get contextual information about any entity (project, task, epic, file, tag). ' +
       'Replaces search_project_context, get_related_files, get_project_overview, get_critical_files, ' +
       'query_project_graph, analyze_impact, get_graph_stats, analyze_project_organization. ' +
       'Use `query` for keyword search, or `entityType` + `entityId` for entity-specific context. ' +
@@ -27,7 +27,7 @@ export const CONTEXT_MANIFEST_TOOLS = [
         },
         entityType: {
           type: 'string',
-          enum: ['project', 'task', 'epic', 'component', 'file', 'tag'],
+          enum: ['project', 'task', 'epic', 'file', 'tag'],
           description: 'Type of entity to get context for',
         },
         entityId: {

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
@@ -126,11 +126,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). ' +

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,7 +10,6 @@
 
 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';
@@ -48,7 +47,6 @@ export const TOOLS = [
   ...AUTH_TOOLS,
   ...ORGANIZATION_TOOLS,
   ...PROJECT_TOOLS,
-  ...COMPONENT_TOOLS,
   ...EPIC_TOOLS,
   ...MILESTONE_TOOLS,
   ...FEATURE_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/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'],