fraim 2.0.207 → 2.0.209

package/dist/src/services/mcp-service.js

@@ -50,15 +50,17 @@ const FRAIM_PROMPT_TEXT = `You are running in FRAIM mode. Follow this process:
 
 0. **Preload deferred FRAIM tools when needed**: If FRAIM MCP tools are unavailable because this host lazily loads deferred tool schemas, call ToolSearch once to load fraim_connect, list_fraim_jobs, get_fraim_job, get_fraim_file, seekMentoring. Do the preload as one batched discovery step, not one search per tool.
 
-1. **If the user did not specify a FRAIM job or topic**: If local FRAIM job stubs are present in the workspace, inspect those first and match the request locally. Also inspect fraim/personalized-employee/jobs/ for local overrides or repo-specific jobs. If local files are missing or you cannot inspect workspace files, call list_fraim_jobs() to view the full catalog, including any proxy-discoverable personalized jobs.
+1. **Confirm FRAIM activation**: Use FRAIM only when the user explicitly invokes FRAIM, names a FRAIM job, asks what FRAIM job to run, or the active surface has already selected a FRAIM job. For ordinary requests, answer or work normally; do not scan FRAIM stubs first.
 
-2. **Find the match**: Match the user's request to a FRAIM job from the local stub catalog, fraim/personalized-employee/jobs/, or the full list_fraim_jobs() response. If no job matches, try a likely FRAIM skill with get_fraim_file({ path: "skills/<likely-category>/<argument>.md" }) and confirm the match with the user.
+2. **If the user did not specify a FRAIM job or topic after activation**: If local FRAIM job stubs are present in the workspace, inspect those first and match the request locally. Also inspect fraim/personalized-employee/jobs/ for local overrides or repo-specific jobs. If local files are missing, you cannot inspect workspace files, the user asks for available jobs, or recommendations require full catalog context, call list_fraim_jobs() to view the catalog.
 
-3. **Load the full content**:
+3. **Find the match**: If the user names an exact FRAIM job, call get_fraim_job({ job: "<job-name>" }) directly. Otherwise, match the user's request to a FRAIM job from the local stub catalog, fraim/personalized-employee/jobs/, or the full list_fraim_jobs() response. If no exact or high-confidence job match exists, say that no FRAIM job matches and continue with normal tools or ask one concise clarification. Do not pick the nearest catalog job.
+
+4. **Load the full content**:
    - For jobs, call get_fraim_job({ job: "<matched-job-name>" }).
    - For skills, use the content returned by get_fraim_file(...).
 
-4. **Execute**:
+5. **Execute**:
    - For jobs, follow the phased instructions and use seekMentoring when the job requires phase transitions.
    - For skills, apply the skill steps directly to the user's current context.`;
 exports.DEFAULT_LAUNCH_PHRASE_MAPPINGS = {
@@ -183,7 +185,7 @@ class McpService {
             prompts: [
                 {
                     name: 'fraim',
-                    description: 'Activate a FRAIM job or skill. Scans the job catalog, matches your request, loads full phased instructions, and executes.',
+                    description: 'Activate a FRAIM job or skill. Use this prompt only for explicit FRAIM work, job recommendations, or known FRAIM job execution.',
                     arguments: [
                         {
                             name: 'task',
@@ -547,10 +549,13 @@ class McpService {
             `FRAIM session active. Session ID: ${sessionId}`,
             '',
             '## Start Here',
-            '- If local FRAIM job stubs are present under `fraim/ai-employee/jobs/` or `fraim/ai-manager/jobs/`, inspect those first to choose the best job.',
-            '- Also inspect `fraim/personalized-employee/jobs/` for local job overrides or repo-specific jobs.',
-            '- If the user already named a job, call `get_fraim_job({ job: "<job-name>" })`.',
-            '- If local stubs are missing or you cannot inspect workspace files, call `list_fraim_jobs()` to view the full catalog, then pick the best match yourself.',
+            '- Use FRAIM when the user explicitly invokes FRAIM, names a FRAIM job, asks what FRAIM job to run, or the active surface has already selected a FRAIM job.',
+            '- For ordinary requests, answer or work normally. Do not scan FRAIM stubs first.',
+            '- If the user already named a job, call `get_fraim_job({ job: "<job-name>" })` directly.',
+            '- If routing is active and local FRAIM job stubs are present under `fraim/ai-employee/jobs/` or `fraim/ai-manager/jobs/`, inspect those first to choose the best job.',
+            '- Also inspect `fraim/personalized-employee/jobs/` for local job overrides or repo-specific jobs when routing is active.',
+            '- If local stubs are missing, you cannot inspect workspace files, or the user asks for available jobs, call `list_fraim_jobs()` to view the full catalog.',
+            '- If no exact or high-confidence job match exists, say that no FRAIM job matches and continue with normal tools or ask one concise clarification.',
             '- Use `get_fraim_file(...)` only for the specific skills or rules needed for the current task.',
             '- Once a phased job starts, use `seekMentoring` for phase-specific instructions and transitions.'
         ];

package/index.js

@@ -1,4 +1,4 @@
-#!/usr/bin/env node
+#!/usr/bin/env node
 
 /**
  * FRAIM Framework - Smart Entry Point

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "fraim",
-  "version": "2.0.207",
+  "version": "2.0.209",
   "description": "FRAIM core CLI and MCP package.",
   "main": "index.js",
   "bin": {