umtri-mcp 1.0.2 → 1.2.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "umtri-mcp",
-  "version": "1.0.2",
+  "version": "1.2.0",
   "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": [

package/server.js

@@ -19,6 +19,7 @@ import { dirname, join } from 'node:path';
 import { createApiClient } from './core/api-client.js';
 import { registerTools } from './core/tools.js';
 import { registerResources } from './core/resources.js';
+import { SERVER_INSTRUCTIONS } from './core/instructions.js';
 
 const __dirname = dirname(fileURLToPath(import.meta.url));
 const RESOURCES_DIR = join(__dirname, 'core', 'resources');
@@ -44,7 +45,7 @@ const api = createApiClient({
 const server = new McpServer({
   name: 'umtri-mcp',
   version: VERSION,
-});
+}, { instructions: SERVER_INSTRUCTIONS });
 
 registerTools(server, { api });
 registerResources(server, { resourcesDir: RESOURCES_DIR });

package/core/resources/seasons-human-only.md

@@ -1,33 +0,0 @@
-# Rule: Seasons Are Created by Humans Only
-
-**AI tools and automation MUST NOT create new seasons.**
-
-## What a season is
-
-A `season` is a deliberate growth epoch declared by a human — for example
-"Q3 2026", "v2 redesign", "post-launch hardening". It is the unit by which
-project owners *consciously break time* in their ground.
-
-## Why this rule exists
-
-Seasons carry intent. They mark moments where a person decides "this chapter
-is done, the next one begins." If an AI agent silently opens a new season
-when it can't decide which existing one to use, the metaphor collapses and
-the project's timeline becomes meaningless noise.
-
-## What this means in practice
-
-- The MCP tool `create_season` is intentionally **not exposed**.
-- When creating a new node and unsure which season it belongs to:
-  - Default to the most recent existing `season` whose state is `now`.
-  - If no `now` season exists, ask the user which season to attach to.
-- Never call `POST /api/projects/:slug/seasons` from automation.
-- A user explicitly saying "create a new season called X" is the only valid
-  trigger. Even then, prefer to confirm before acting.
-
-## What is allowed
-
-- Reading seasons (`list_seasons`).
-- Attaching new nodes to existing seasons via `season` field.
-- Suggesting to the user that a new season *might* be useful — but waiting
-  for them to create it.