create-merlin-brain 5.4.2 → 5.4.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -286,7 +286,7 @@ _badge_prefix=$(echo "${_badge}" | sed 's/MERLIN.*//' 2>/dev/null || true)
|
|
|
286
286
|
_banner="${_badge_prefix}MERLIN · connected · ${_project_name} | Mode: ${_mode_label} · Codex: ${_codex_label} | Next: ${_next_action}"
|
|
287
287
|
|
|
288
288
|
# ── 4b. Build the additionalContext with banner + routing rules ─
|
|
289
|
-
_context="${_banner} || STOP. Your FIRST action must be: call
|
|
289
|
+
_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."
|
|
290
290
|
_context="${_context} AFTER BOOT — MANDATORY ROUTING (you MUST follow this, do NOT skip):"
|
|
291
291
|
_context="${_context} Bug/crash/error logs/deploy failure: use Skill(merlin:workflow, args=run bug-fix <summary>)."
|
|
292
292
|
_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
|
|
|
303
303
|
jq -n --arg ctx "$_context" '{hookSpecificOutput:{hookEventName:"SessionStart",additionalContext:$ctx}}'
|
|
304
304
|
else
|
|
305
305
|
# Fallback: simple printf with no special chars
|
|
306
|
-
printf '{"hookSpecificOutput":{"hookEventName":"SessionStart","additionalContext":"STOP.
|
|
306
|
+
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}"
|
|
307
307
|
fi
|
|
308
308
|
|
|
309
309
|
exit 0
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
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.
|
|
1
|
+
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.
|
|
2
2
|
|
|
3
3
|
## Duo mode (codex+codex)
|
|
4
4
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "create-merlin-brain",
|
|
3
|
-
"version": "5.4.
|
|
3
|
+
"version": "5.4.3",
|
|
4
4
|
"description": "Merlin - The Ultimate AI Brain for Claude Code, Codex, and other AI CLIs. One install: workflows, agents, loop, and Sights MCP server.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"main": "./dist/server/index.js",
|