opencode-orchestrator 0.1.9 → 0.1.20

package/README.md

@@ -6,8 +6,8 @@
 
 [![MIT License](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
 [![npm](https://img.shields.io/npm/v/opencode-orchestrator.svg)](https://www.npmjs.com/package/opencode-orchestrator)
+[![npm downloads](https://img.shields.io/npm/dt/opencode-orchestrator.svg)](https://www.npmjs.com/package/opencode-orchestrator)
 [![OpenCode Plugin](https://img.shields.io/badge/OpenCode-Plugin-purple.svg)](https://opencode.ai)
-
 </div>
 
 ---
@@ -27,7 +27,7 @@ A 6-agent collaborative system that turns any LLM into a reliable coding team.
 | One big prompt → Hope it works | Atomic tasks → Verified every step |
 | Expensive model required | Any model works |
 | Errors compound silently | Self-correcting loop |
-| Unpredictable results | Consistent quality |
+| Unpredictable results | **Relentless execution until success** |
 
 ---
 
@@ -37,8 +37,8 @@ A 6-agent collaborative system that turns any LLM into a reliable coding team.
 - **🧠 Micro-Task Architecture** — Atomic task decomposition for reliability
 - **🔄 Self-Correcting Loop** — Every change reviewed, errors auto-fixed
 - **👥 6-Agent Team** — Specialized roles working together
-- **🛡️ Circuit Breaker** — Stops after 3 same errors, prevents infinite loops
-- **⚡ Full Autonomy** — `/auto` command handles everything
+- **🛡️ Resilient Execution** — Never stops on errors. Pivots strategy (Plan/Search) until success.
+- **⚡ Full Autonomy** — `/auto` is all you need. Relentless execution until 100% complete.
 
 ---
 
@@ -59,7 +59,7 @@ User Request
 │   Search → Code → Review → Fix           │
 │       ↑                      │           │
 │       └──────────────────────┘           │
-│           (until PASS)                   │
+│           (Never gives up)               │
 └──────────────────────────────────────────┘
      │
      ▼

package/dist/index.js

@@ -12348,6 +12348,7 @@ var AGENTS = {
 ## Mission
 Coordinate agents to complete user tasks with ZERO errors.
 Keep iterating until the task is 100% complete and working.
+FAILURE IS NOT AN OPTION. If you get stuck, change strategy.
 
 ## Your Team
 - **planner**: Decomposes complex tasks into atomic units
@@ -12364,7 +12365,7 @@ Keep iterating until the task is 100% complete and working.
    b. CODE: Call coder with single atomic task
    c. VERIFY: Call reviewer (MANDATORY after every code change)
    d. FIX: If reviewer finds error \u2192 call fixer \u2192 verify again
-   e. LOOP: Repeat fix/verify until PASS (max 3 attempts)
+   e. LOOP: Repeat fix/verify until PASS.
 4. NEXT: Move to next task only after current passes
 5. COMPLETE: All tasks done with all reviews passed
 
@@ -12376,22 +12377,24 @@ Keep iterating until the task is 100% complete and working.
 \u274C "Refactor the entire auth module" (too big)
 \u274C "Fix all bugs" (not atomic)
 
-## Error Recovery Protocol
+## Error Recovery Protocol (Resilient Mode)
 - Error from reviewer \u2192 Call fixer with EXACT error details
-- Same error 3 times \u2192 STOP, report to user, suggest alternatives
+- Same error 3 times \u2192 DO NOT STOP.
+  - Option A: Call searcher to find better context/examples
+  - Option B: Call planner to break task down further
+  - Option C: Try a completely different implementation approach
 - Coder confused \u2192 Provide more context from searcher
-- Stuck on approach \u2192 Try different strategy
 
 ## Progress Tracking (show after each step)
 \uD83D\uDCCB Task: [current task]
 \u2705 Completed: [list]
 \u23F3 Remaining: [list]
-\uD83D\uDD04 Retry: [X/3] if applicable
+\uD83D\uDD04 Retry: [X] (Reset counter if strategy changes)
 
 ## Critical Rules
 - NEVER skip reviewer after code changes
 - One atomic task at a time
-- Stop if same error persists 3 times
+- NEVER GIVE UP. Find a way.
 - Always show progress`,
     canWrite: false,
     canBash: false
@@ -12547,7 +12550,17 @@ Find ALL issues in the code. Be thorough but specific.
 - Consistent naming
 - Proper indentation
 
-### 6. Security (if applicable)
+### 1. Syntax & Formatting (Top Priority)
+- All brackets paired: { } ( ) [ ]
+- Indentation is consistent
+- Semicolons present where needed
+- No obvious syntax typos
+
+### 2. Consistency & Sync (Critical)
+- Export/Import names match EXACTLY
+- Function signatures match usage (arguments, return types)
+
+### 7. Security (if applicable)
 - No hardcoded secrets
 - Input validation present
 
@@ -12557,7 +12570,11 @@ Find ALL issues in the code. Be thorough but specific.
 \`\`\`
 \u2705 PASS
 
-Reviewed: [what was checked]
+Summary:
+- Checked syntax, types, and imports
+- Verified export/import name consistency
+- Confirmed logic implementation
+
 Status: All checks passed
 \`\`\`
 
@@ -12565,10 +12582,11 @@ Status: All checks passed
 \`\`\`
 \u274C FAIL
 
-[ERROR-001] <category>
+[ERROR-001] <category: Syntax | Type | Name Mismatch | Import | Logic>
 \u251C\u2500\u2500 File: <path>
 \u251C\u2500\u2500 Line: <number>
 \u251C\u2500\u2500 Issue: <specific problem>
+\u251C\u2500\u2500 Root Cause: <Typo / Sync Mismatch / Logic Error>
 \u251C\u2500\u2500 Found: \`<problematic code>\`
 \u251C\u2500\u2500 Expected: \`<correct code>\`
 \u2514\u2500\u2500 Fix: <exact fix instruction>
@@ -12577,10 +12595,10 @@ Status: All checks passed
 \`\`\`
 
 ## Rules
-- List ALL errors found (not just first one)
-- Be SPECIFIC about location and fix
-- Prioritize: Syntax > Types > Logic > Style
-- For each error, provide exact fix instruction`,
+- Check specifically for 'Name Mismatch' (e.g., export 'foo' vs import 'Foo')
+- Verify function signatures match calls
+- List ALL errors found
+- Be SPECIFIC about location and fix`,
     canWrite: false,
     canBash: true
   },
@@ -12605,26 +12623,30 @@ You receive error reports like:
 \`\`\`
 
 ## Fixing Process
-1. Read each error carefully
-2. Understand root cause
-3. Apply minimal fix
-4. Verify fix addresses the issue
+1. ANALYZE: Read errors and identify if it's a simple typo, sync issue, or logic bug.
+2. SUMMARIZE: Briefly state what went wrong (e.g., "Export name mismatch in api.ts").
+3. FIX: Apply minimal fix to address the root cause.
+4. VERIFY: Ensure fix doesn't create new issues.
 
 ## Rules
 - Fix ALL reported errors
 - Make MINIMAL changes
 - Don't "improve" unrelated code
-- Don't refactor while fixing
+- Check for name mismatches (case sensitivity)
 - Keep existing style
+- **ANTI-OVERENGINEERING**:
+  - If Syntax/Indent error: ONLY fix the character/spacing. NO logic changes.
+  - If Typo: ONLY fix the name.
 
 ## Output Format
-\`\`\`<language>
-// Fixed code with all errors addressed
 \`\`\`
+### Analysis
+- [ERROR-001]: <cause> (e.g., Missing closing brace at line 42)
 
-### Changes Made
-- [ERROR-001]: <what was fixed>
-- [ERROR-002]: <what was fixed>
+### Fixes Applied
+\`\`\`<language>
+// Fixed code
+\`\`\`
 
 ## If Fix Unclear
 - Ask for clarification
@@ -12796,8 +12818,7 @@ Execute according to your role. Be thorough and precise.
 var COMMANDS = {
   auto: {
     description: "Autonomous execution with self-correcting loop",
-    template: `<command-instruction>
-\uD83D\uDE80 AUTO MODE - Self-Correcting Agent Loop
+    template: `\uD83D\uDE80 AUTO MODE - Self-Correcting Agent Loop
 
 ## Protocol
 1. Call planner to decompose into atomic tasks
@@ -12805,18 +12826,18 @@ var COMMANDS = {
    - Call searcher if context needed
    - Call coder to implement
    - Call reviewer to verify (MANDATORY)
-   - If FAIL: Call fixer \u2192 reviewer again (max 3 retries)
+   - If FAIL: Call fixer \u2192 reviewer again
    - If PASS: Move to next task
 3. Continue until all tasks complete with PASS
 
-## Error Recovery
-- Same error 3x \u2192 Stop and ask user
-- New error \u2192 Apply fix and retry
-- Stuck \u2192 Try different approach
+## Error Recovery (Resilient Strategy)
+- Same error 3x \u2192 DO NOT STOP.
+- Resolve the blocker by finding more context or breaking down the task.
+- Keep iterating until the task is 100% COMPLETE and VERIFIED.
 
 ## Goal
-Complete "$ARGUMENTS" with zero errors.
-Keep iterating until done.
+Complete "$ARGUMENTS" with ZERO errors.
+Relentless execution until absolute success.
 </command-instruction>
 
 <user-task>
@@ -12996,12 +13017,13 @@ Review progress and continue manually.`;
         const retries = (session.taskRetries.get(errorId) || 0) + 1;
         session.taskRetries.set(errorId, retries);
         if (retries >= state.maxRetries) {
-          session.enabled = false;
           output.output += `
 
 \u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501
-\uD83D\uDED1 RETRY LIMIT (${state.maxRetries}x same error)
-Review manually or try different approach.`;
+\u26A0\uFE0F RETRY LIMIT (${state.maxRetries}x)
+DO NOT GIVE UP.
+SYSTEM ALERT: Stop repeating the same fix.
+REQUIRED: Call 'planner' (break down) or 'searcher' (find context) NOW.`;
           return;
         }
         output.output += `

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "opencode-orchestrator",
-    "version": "0.1.9",
+    "version": "0.1.20",
     "description": "6-Agent collaborative architecture for OpenCode - Make any model reliable",
     "author": "agnusdei1207",
     "license": "MIT",
@@ -54,7 +54,7 @@
         "release:patch": "bun run build:full && bun run test && bun run version:patch && bun run publish:npm && bun run release:git",
         "release:minor": "bun run build:full && bun run test && bun run version:minor && bun run publish:npm && bun run release:git",
         "release:major": "bun run build:full && bun run test && bun run version:major && bun run publish:npm && bun run release:git",
-        "release:git": "git add -A && git commit -m \"Release v$(node -p \"require('./package.json').version\")\" && git tag \"v$(node -p \"require('./package.json').version\")\" && git push && git push --tags",
+        "release:git": "git add -A && git commit -m \"Release v$(node -p \"require('./package.json').version\")\" && git tag \"v$(node -p \"require('./package.json').version\")\" && git push && git push --tags && gh release create \"v$(node -p \"require('./package.json').version\")\" bin/orchestrator --title \"v$(node -p \"require('./package.json').version\")\" --generate-notes",
         "postinstall": "node dist/scripts/postinstall.js 2>/dev/null || true"
     },
     "dependencies": {