umtri-mcp 1.3.1 → 1.3.3

package/core/resources/plan.md

@@ -35,7 +35,9 @@ back onto the nodes. The human commits when satisfied.
    unless the node already has `metadata.implements`** (step 3), so attach the
    source paths first. The human can also commit from the UI. If you are unsure
    the realization is complete, leave it as plan and ask the human rather than
-   committing.
+   committing. **Commit from the top down:** a node whose parent is still a plan
+   is rejected — commit the parent first. (A committed node under a plan parent
+   would vanish from the tree whenever Plan mode is off.)
 6. **Record the commit (CI/CD form record).** When the code lands in git, the
    commit is recorded onto the nodes it touched via `record_commit`
    (sha + changed files → appended to each matching node's `metadata.commits`).

package/core/tools.js

@@ -814,7 +814,7 @@ export function registerTools(server, { api }) {
     'commit_plan',
     {
       title: 'Commit a realized plan node',
-      description: 'Promotes a plan node (metadata.plan=true) to the real tree by clearing the plan flag. VERIFICATION GATE: the node must already carry metadata.implements (the source path(s) you wrote) — without it the commit is rejected, because an uncommitted plan node with no implements is not considered realized. Call this only after you have actually written the code and recorded implements via update_node. See umtri://rules/plan.',
+      description: 'Promotes a plan node (metadata.plan=true) to the real tree by clearing the plan flag. VERIFICATION GATE: the node must already carry metadata.implements (the source path(s) you wrote) — without it the commit is rejected, because an uncommitted plan node with no implements is not considered realized. Call this only after you have actually written the code and recorded implements via update_node. Commit from the top down: a node whose parent is still a plan is rejected — commit the parent first. See umtri://rules/plan.',
       inputSchema: z.object({
         slug: z.string().min(1).describe('Ground slug.'),
         id: z.string().min(1).describe('Plan node id to commit.'),
@@ -857,7 +857,10 @@ export function registerTools(server, { api }) {
         slug: z.string().min(1).describe('Ground slug.'),
         source: z.string().min(1).describe('Source node id.'),
         target: z.string().min(1).describe('Target node id.'),
-        type: z.string().optional().describe('Edge type. Backend defaults if omitted.'),
+        // 서버(store.createEdge)가 type을 필수로 요구한다. 예전엔 optional + "Backend defaults"라고
+        // 안내해 생략한 에이전트가 매번 한 번씩 거부당했다. 그라운드마다 edge_types가 있어 enum으로
+        // 못 박지 않고 필수 문자열로 둔다.
+        type: z.string().min(1).describe('Edge type — required. "dependency" (source is built on / needs target) or "data_flow" (data moves source → target) — use one of the ground\'s edgeTypes.'),
         label: z.string().optional(),
         metadata: z.record(z.any()).optional(),
       }),
@@ -867,8 +870,7 @@ export function registerTools(server, { api }) {
         const { ok, rejectReason } = validateEdge({ sourceId: source, targetId: target });
         if (!ok) throw new Error(`Rejected by protocol: ${rejectReason}`);
 
-        const body = { source, target };
-        if (type !== undefined) body.type = type;
+        const body = { source, target, type };
         if (label !== undefined) body.label = label;
         if (metadata !== undefined) body.metadata = metadata;
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "umtri-mcp",
-  "version": "1.3.1",
+  "version": "1.3.3",
   "description": "MCP server for Umtri — give your AI coding agent a persistent map of your project's structure, dependencies, and bugs.",
   "mcpName": "io.umtri/umtri",
   "keywords": [