umtri-mcp 1.3.0 → 1.3.2

package/core/resources/plan.md

@@ -26,6 +26,10 @@ back onto the nodes. The human commits when satisfied.
    didn't draw (child leaves/veins, an extra twig), create them with
    `metadata.plan = true` too — everything you add stays reviewable until the
    human commits. Do not create finalized (non-plan) nodes during realization.
+   **Except a trunk:** trunks are the frame of the tree and are never plan —
+   `create_node`/`update_node` reject a trunk with `metadata.plan`. If the brief
+   needs a new trunk (a new app or service), ask the human to add it; then
+   draw the plan as limbs under it.
 5. **Commit when realized.** Promote a plan node to the real tree with
    `commit_plan` — it clears `metadata.plan`. The tool **rejects the commit
    unless the node already has `metadata.implements`** (step 3), so attach the

package/core/tools.js

@@ -660,7 +660,7 @@ export function registerTools(server, { api }) {
         'The tool validates against protocol policies. Hierarchy violations are rejected. Soft issues (reserved-domain labels, leaf↔vein heuristic, trunk naming) come back as warnings in the response — reconsider before continuing if warnings appear.',
         'After creating a leaf/vein, consider its connections: if it calls/feeds another node add an api (create_api), if it depends on/is built on another add an edge (create_edge). The response carries a connectionCheck reminder. See umtri://rules/system-structure (Connections).',
         'Do not open a new season just because none fits — attach to the now-season, or ask the user. create_season needs their confirmation (umtri://rules/seasons).',
-        'When realizing a human-drawn plan brief, any detail nodes you add should carry metadata.plan=true and the realized node needs metadata.implements — see umtri://rules/plan.',
+        'When realizing a human-drawn plan brief, any detail nodes you add should carry metadata.plan=true and the realized node needs metadata.implements — see umtri://rules/plan. A trunk is never plan: metadata.plan on a trunk is rejected.',
       ].join(' '),
       inputSchema: z.object({
         slug: z.string().min(1).describe('Ground slug.'),
@@ -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.0",
+  "version": "1.3.2",
   "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": [