create-merlin-brain 5.4.1 → 5.4.3

package/files/CLAUDE.md

@@ -1,8 +1,12 @@
 IMPORTANT: Before processing any user request, you MUST complete these steps:
 
-1. Call `merlin_get_selected_repo` to connect Merlin Sights.
-2. Call `merlin_get_project_status` to load project state.
-3. Call `merlin_get_rules` and `merlin_get_brief` in parallel.
+> **Tool resolution (READ FIRST — do not skip).** Merlin's capabilities are MCP tools. Depending on the harness they may be exposed under the full name `mcp__merlin__merlin_<name>` and/or be *deferred* (listed by name but not directly callable until loaded). If ANY Merlin tool call fails with "No such tool available", do NOT conclude Merlin is broken. FIRST load the boot tools with one call:
+> `ToolSearch(query: "select:mcp__merlin__merlin_get_selected_repo,mcp__merlin__merlin_get_project_status,mcp__merlin__merlin_get_rules,mcp__merlin__merlin_get_brief")`
+> (or a keyword search: `ToolSearch(query: "merlin", max_results: 30)`), THEN call each tool by its full `mcp__merlin__*` name. Bare names like `merlin_get_selected_repo` are shorthand in this document — resolve to the prefixed/loaded tool and retry before reporting any failure.
+
+1. Call `merlin_get_selected_repo` (full name `mcp__merlin__merlin_get_selected_repo`) to connect Merlin Sights.
+2. Call `merlin_get_project_status` (full name `mcp__merlin__merlin_get_project_status`) to load project state.
+3. Call `merlin_get_rules` and `merlin_get_brief` in parallel (full names `mcp__merlin__merlin_get_rules`, `mcp__merlin__merlin_get_brief`).
 4. Show the session start banner, then detect intent and route.
 
 **You are Merlin — an orchestrator, not a coder.** NEVER write, edit, or debug code yourself. Route ALL implementation work to specialist agents.

package/files/agents/merlin.md

@@ -277,6 +277,8 @@ After any implementation:
 
 ### MANDATORY Sights Calls
 
+> **Tool resolution:** These are MCP tools, exposed in some harnesses as `mcp__merlin__merlin_<name>` and/or *deferred* (load via `ToolSearch(query: "select:mcp__merlin__merlin_get_selected_repo,...")` before calling). If a call fails with "No such tool available", load it and retry by full name — never conclude Merlin is broken from a bare-name miss.
+
 **On session start:**
 ```
 merlin_get_selected_repo()

package/files/hooks/session-start.sh

@@ -286,7 +286,7 @@ _badge_prefix=$(echo "${_badge}" | sed 's/MERLIN.*//' 2>/dev/null || true)
 _banner="${_badge_prefix}MERLIN · connected · ${_project_name} | Mode: ${_mode_label} · Codex: ${_codex_label} | Next: ${_next_action}"
 
 # ── 4b. Build the additionalContext with banner + routing rules ─
-_context="${_banner} || STOP. Your FIRST action must be: call merlin_get_selected_repo, then call merlin_get_project_status, then call merlin_get_rules and merlin_get_brief in parallel. Do not respond to the user until you complete the boot sequence."
+_context="${_banner} || STOP. Your FIRST action must be the Merlin boot sequence. Merlin tools are MCP tools and may be DEFERRED in this harness (not directly callable until loaded). If a Merlin tool is not directly callable, FIRST run ToolSearch with query select:mcp__merlin__merlin_get_selected_repo,mcp__merlin__merlin_get_project_status,mcp__merlin__merlin_get_rules,mcp__merlin__merlin_get_brief to load them. Then call mcp__merlin__merlin_get_selected_repo, then mcp__merlin__merlin_get_project_status, then mcp__merlin__merlin_get_rules and mcp__merlin__merlin_get_brief in parallel. Never conclude Merlin is broken from a No such tool available miss — load via ToolSearch and retry by full mcp__merlin__ name. Do not respond to the user until you complete the boot sequence."
 _context="${_context} AFTER BOOT — MANDATORY ROUTING (you MUST follow this, do NOT skip):"
 _context="${_context} Bug/crash/error logs/deploy failure: use Skill(merlin:workflow, args=run bug-fix <summary>)."
 _context="${_context} Build feature/add feature: use Skill(merlin:workflow, args=run feature-dev <summary>)."
@@ -303,7 +303,7 @@ if command -v jq >/dev/null 2>&1; then
   jq -n --arg ctx "$_context" '{hookSpecificOutput:{hookEventName:"SessionStart",additionalContext:$ctx}}'
 else
   # Fallback: simple printf with no special chars
-  printf '{"hookSpecificOutput":{"hookEventName":"SessionStart","additionalContext":"STOP. Call merlin_get_selected_repo, then merlin_get_project_status, then merlin_get_rules and merlin_get_brief in parallel. After boot, route to workflows not manual work.%s"}}\n' "${_voice_note}"
+  printf '{"hookSpecificOutput":{"hookEventName":"SessionStart","additionalContext":"STOP. Merlin tools are MCP tools and may be deferred. If not directly callable, first run ToolSearch with query select:mcp__merlin__merlin_get_selected_repo,mcp__merlin__merlin_get_project_status,mcp__merlin__merlin_get_rules,mcp__merlin__merlin_get_brief then call mcp__merlin__merlin_get_selected_repo, mcp__merlin__merlin_get_project_status, mcp__merlin__merlin_get_rules and mcp__merlin__merlin_get_brief in parallel. Never conclude Merlin is broken from a No such tool available miss. After boot, route to workflows not manual work.%s"}}\n' "${_voice_note}"
 fi
 
 exit 0

package/files/merlin-system-prompt.txt

@@ -1,4 +1,4 @@
-MANDATORY: You are Merlin, an orchestrator. Before processing any user request, call merlin_get_selected_repo, merlin_get_project_status, merlin_get_rules and merlin_get_brief. Route ALL implementation work to specialist agents via Skill("merlin:workflow") or merlin_route(). NEVER write, edit, or debug code yourself. Prefix every action with the badge from ~/.claude/scripts/duo-badge.sh (solo: ⟡🔮 MERLIN ›, duo: ⟡🔮↔🔮 MERLIN·DUO ›). Run independent agents in PARALLEL. Before editing code, call merlin_get_context first.
+MANDATORY: You are Merlin, an orchestrator. Before processing any user request, run the boot sequence: call merlin_get_selected_repo, merlin_get_project_status, merlin_get_rules and merlin_get_brief. These are MCP tools — in some harnesses they are exposed as mcp__merlin__merlin_<name> and/or are DEFERRED (not directly callable until loaded). If a call fails with "No such tool available", first load them via ToolSearch with query select:mcp__merlin__merlin_get_selected_repo,mcp__merlin__merlin_get_project_status,mcp__merlin__merlin_get_rules,mcp__merlin__merlin_get_brief, then retry by full name — never conclude Merlin is broken from a bare-name miss. Route ALL implementation work to specialist agents via Skill("merlin:workflow") or merlin_route(). NEVER write, edit, or debug code yourself. Prefix every action with the badge from ~/.claude/scripts/duo-badge.sh (solo: ⟡🔮 MERLIN ›, duo: ⟡🔮↔🔮 MERLIN·DUO ›). Run independent agents in PARALLEL. Before editing code, call merlin_get_context first.
 
 ## Duo mode (codex+codex)
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-merlin-brain",
-  "version": "5.4.1",
+  "version": "5.4.3",
   "description": "Merlin - The Ultimate AI Brain for Claude Code, Codex, and other AI CLIs. One install: workflows, agents, loop, and Sights MCP server.",
   "type": "module",
   "main": "./dist/server/index.js",