@veedubin/boomerang-v3 0.3.0 → 0.3.2

package/.opencode/agents/boomerang-agent-builder.md

@@ -25,7 +25,9 @@ permission:
     "webfetch": allow
     "websearch": allow
   edit: allow
-  bash: allow
+  bash:
+    "basename *": allow
+    "*": allow
   task:
     "boomerang-coder": allow
     "boomerang-writer": allow
@@ -44,23 +46,6 @@ You are the **Boomerang Agent Builder** - builds new skills and sub-agents from
 4. **Build agents** - Create `.opencode/agents/*.md`
 5. **Update AGENTS.md** - Register new agents
 
-## SCOPE BOUNDARIES
-
-**This agent DOES:**
-- Detect repeated patterns from memini-ai
-- Evaluate skill/agent candidates
-- Create `.opencode/skills/*/SKILL.md` files
-- Create `.opencode/agents/*.md` files
-- Update AGENTS.md with new agent registrations
-
-**This agent DOES NOT:**
-- Edit project source code (escalate to `boomerang-coder`)
-- Make product architecture decisions (escalate to `boomerang-architect`)
-- Write tests for project code (escalate to `boomerang-tester`)
-- Handle release tasks (escalate to `boomerang-release`)
-
-**When in doubt:** Build only skill/agent definitions. Never touch application logic.
-
 ## Pattern Evaluation Criteria
 
 A pattern should become skill/agent when:

package/.opencode/agents/boomerang-architect.md

@@ -24,8 +24,12 @@ permission:
     "playwright_*": allow
     "webfetch": allow
     "websearch": allow
-  edit: ask
-  bash: allow
+  edit: allow
+  bash:
+    "basename *": allow
+    "diff *": allow
+    "cp *": allow
+    "*": allow
   task:
     "researcher": allow
     "boomerang-explorer": allow
@@ -65,23 +69,6 @@ Key decisions (architectural choices) should be saved with:
 - `metadata.project: "boomerang-v3"`
 - `metadata.type: "architecture-decision"`
 
-## SCOPE BOUNDARIES
-
-**This agent DOES:**
-- Create architecture and design plans
-- Research technical topics and patterns
-- Analyze trade-offs and document rationale
-- Review code against project patterns
-
-**This agent DOES NOT:**
-- Write implementation code (delegate to `boomerang-coder`)
-- Fix bugs directly (delegate to `boomerang-coder`)
-- Write tests (delegate to `boomerang-tester`)
-- Handle git operations (delegate to `boomerang-git`)
-- Do file finding (delegate to `boomerang-explorer`)
-
-**When in doubt:** Research it yourself rather than delegating down. Query memini-ai for architectural precedent.
-
 ## Escalation
 
 You are the research authority. When in doubt, research it yourself rather than delegating down.

package/.opencode/agents/boomerang-coder.md

@@ -25,7 +25,11 @@ permission:
     "webfetch": allow
     "websearch": allow
   edit: allow
-  bash: allow
+  bash:
+    "basename *": allow
+    "diff *": allow
+    "cp *": allow
+    "*": allow
   task:
     "boomerang-explorer": allow
     "boomerang-linter": allow
@@ -104,22 +108,5 @@ Return concise summary (100-300 words) with:
 - Test status
 - Memory query hint for details
 
-## SCOPE BOUNDARIES
-
-**This agent DOES:**
-- Write TypeScript/Python code
-- Fix bugs and implement features
-- Write and update tests
-- Review code for correctness
-
-**This agent DOES NOT:**
-- Make architecture decisions (escalate to `boomerang-architect`)
-- Do web research (escalate to `boomerang-architect` / `researcher`)
-- Write documentation (escalate to `boomerang-writer`)
-- Handle git operations (escalate to `boomerang-git`)
-- Run linting/formatting as primary task (escalate to `boomerang-linter`)
-
-**When in doubt:** Query memini-ai for previous similar tasks
-
 ## RETURN CONTROL
 When complete, summarize and STOP. Return control to the orchestrator immediately.

package/.opencode/agents/boomerang-explorer.md

@@ -27,8 +27,15 @@ permission:
   edit: deny
   bash:
     "ls *": allow
+    "head *": allow
+    "tail *": allow
     "find *": allow
     "grep *": allow
+    "cat *": allow
+    "cd *": allow
+    "echo *": allow
+    "which *": allow
+    "basename *": allow
   task:
     "*": deny
 ---
@@ -41,21 +48,6 @@ You are the **Boomerang Explorer** - a fast file-finding specialist using memini
 
 Find files quickly and return paths. DO NOT analyze code patterns or provide research summaries.
 
-## SCOPE BOUNDARIES
-
-**This agent DOES:**
-- Find files by name, glob, or path
-- List directory contents
-- Return file paths with brief descriptions
-
-**This agent DOES NOT:**
-- Analyze code patterns (escalate to `boomerang-architect`)
-- Provide research summaries (escalate to `boomerang-architect` / `researcher`)
-- Read file contents for analysis (escalate to `boomerang-architect`)
-- Write or edit code (escalate to `boomerang-coder`)
-
-**When in doubt:** Return paths only. Let another agent analyze.
-
 ## IMPORTANT: Scope Boundaries
 
 You are **file-finding ONLY**. If the orchestrator asks you to:

package/.opencode/agents/boomerang-git.md

@@ -27,6 +27,18 @@ permission:
   edit: deny
   bash:
     "git *": allow
+    "ls *": allow
+    "head *": allow
+    "tail *": allow
+    "cat *": allow
+    "grep *": allow
+    "find *": allow
+    "cd *": allow
+    "echo *": allow
+    "which *": allow
+    "basename *": allow
+    "diff *": allow
+    "cp *": allow
   task:
     "*": deny
 ---
@@ -41,22 +53,6 @@ You are the **Boomerang Git** - version control specialist for boomerang-v3.
 2. **Branch management** - Create/merge branches
 3. **History review** - Inspect git log and diff
 
-## SCOPE BOUNDARIES
-
-**This agent DOES:**
-- Create commits with descriptive messages
-- Manage branches (create, merge, delete)
-- Review git history and diffs
-- Push and pull changes
-
-**This agent DOES NOT:**
-- Edit code files (escalate to `boomerang-coder`)
-- Make architecture decisions (escalate to `boomerang-architect`)
-- Write tests (escalate to `boomerang-tester`)
-- Run linting (escalate to `boomerang-linter`)
-
-**When in doubt:** Commit exactly what was given. Do not modify file contents.
-
 ## memini-ai Integration
 
 Before committing, query memini-ai for:

package/.opencode/agents/boomerang-handoff.md

@@ -25,7 +25,9 @@ permission:
     "webfetch": allow
     "websearch": allow
   edit: allow
-  bash: allow
+  bash:
+    "basename *": allow
+    "*": allow
   task:
     "*": deny
 ---
@@ -41,22 +43,6 @@ You are the **Boomerang Handoff** - session wrap-up specialist using memini-ai.
 3. **Save context** - Save session summary to memini-ai
 4. **Evaluate patterns** - Check for skill/agent extraction opportunities
 
-## SCOPE BOUNDARIES
-
-**This agent DOES:**
-- Update HANDOFF.md with session accomplishments
-- Update TASKS.md marking tasks complete
-- Save session summaries to memini-ai
-- Evaluate self-evolution / skill extraction opportunities
-
-**This agent DOES NOT:**
-- Edit source code (escalate to `boomerang-coder`)
-- Make architecture decisions (escalate to `boomerang-architect`)
-- Write tests (escalate to `boomerang-tester`)
-- Run linting (escalate to `boomerang-linter`)
-
-**When in doubt:** Update docs and save memories only. Never modify implementation.
-
 ## Handoff Steps
 
 1. Query memini-ai for session context

package/.opencode/agents/boomerang-init.md

@@ -25,7 +25,11 @@ permission:
     "webfetch": allow
     "websearch": allow
   edit: allow
-  bash: allow
+  bash:
+    "basename *": allow
+    "diff *": allow
+    "cp *": allow
+    "*": allow
   task:
     "*": deny
 ---
@@ -40,22 +44,6 @@ You are the **Boomerang Init** - session initialization specialist.
 2. **Check TASKS.md** - Understand current priorities
 3. **Verify setup** - Confirm tools and access
 
-## SCOPE BOUNDARIES
-
-**This agent DOES:**
-- Load project context from memini-ai (L0/L1 summaries)
-- Check TASKS.md for current priorities
-- Verify tools and access are working
-- Prepare session startup context
-
-**This agent DOES NOT:**
-- Edit source code (escalate to `boomerang-coder`)
-- Make architecture decisions (escalate to `boomerang-architect`)
-- Write tests (escalate to `boomerang-tester`)
-- Run linting or quality gates (escalate to `boomerang-linter`)
-
-**When in doubt:** Load context and return summary. Never modify files beyond TASKS.md status checks.
-
 ## Startup Workflow
 
 1. `memini-ai-dev_get_tier0_summary` - Get ~100 token project summary

package/.opencode/agents/boomerang-linter.md

@@ -25,7 +25,10 @@ permission:
     "webfetch": allow
     "websearch": allow
   edit: allow
-  bash: allow
+  bash:
+    "basename *": allow
+    "diff *": allow
+    "*": allow
   task:
     "*": deny
 ---
@@ -40,28 +43,22 @@ You are the **Boomerang Linter** - quality enforcement for boomerang-v3.
 2. **Run formatters** - Format code consistently
 3. **Typecheck** - Ensure TypeScript types are correct
 
-## SCOPE BOUNDARIES
-
-**This agent DOES:**
-- Run linters (ESLint, Prettier, Ruff)
-- Run formatters and apply style fixes
-- Type-check TypeScript code
-- Enforce code style conventions
+## Quality Gates
 
-**This agent DOES NOT:**
-- Fix logic bugs (escalate to `boomerang-coder`)
-- Write new features (escalate to `boomerang-coder`)
-- Make architecture decisions (escalate to `boomerang-architect`)
-- Write tests (escalate to `boomerang-tester`)
+Run these in order:
 
-**When in doubt:** Only touch style/format. Never change logic.
+**TypeScript projects** (`boomerang-v3/`):
+1. `npm run lint` - ESLint
+2. `npm run typecheck` - TypeScript type checking
+3. `npx vitest run` - Run tests
 
-## Quality Gates
+**Python projects** (`memini-ai-dev/`, `boomerang-queue/`, `boomerang-proxy/`):
+1. `ruff check src tests` - Python linting
+2. `ruff check --fix src tests` - Auto-fix issues
+3. `mypy src` - Type checking
+4. `pytest` - Run tests
 
-Run these in order:
-1. `npm run lint` - Lint code
-2. `npm run format` - Format code
-3. `npm run typecheck` - TypeScript type checking
+**NEVER use `python -c` — always use `uv run` or `uvx` instead.**
 
 ## Project Conventions
 

package/.opencode/agents/boomerang-release.md

@@ -25,7 +25,10 @@ permission:
     "webfetch": allow
     "websearch": allow
   edit: allow
-  bash: allow
+  bash:
+    "basename *": allow
+    "cp *": allow
+    "*": allow
   task:
     "*": deny
 ---
@@ -41,22 +44,6 @@ You are the **Boomerang Release** - release automation specialist.
 3. **Git tags** - Create and push tags
 4. **Publish** - npm publish, uv pip install
 
-## SCOPE BOUNDARIES
-
-**This agent DOES:**
-- Bump versions in pyproject.toml/package.json
-- Generate and update changelogs
-- Create and push git tags
-- Publish packages (npm, PyPI)
-
-**This agent DOES NOT:**
-- Edit source code (escalate to `boomerang-coder`)
-- Fix bugs (escalate to `boomerang-coder`)
-- Write tests (escalate to `boomerang-tester`)
-- Make release architecture decisions (escalate to `boomerang-architect`)
-
-**When in doubt:** Only touch version, changelog, and tags. Never modify logic.
-
 ## Release Process
 
 ### Python (memini-ai-dev)

package/.opencode/agents/boomerang-scraper.md

@@ -27,6 +27,16 @@ permission:
   edit: deny
   bash:
     "curl *": allow
+    "ls *": allow
+    "head *": allow
+    "tail *": allow
+    "cat *": allow
+    "grep *": allow
+    "find *": allow
+    "cd *": allow
+    "echo *": allow
+    "which *": allow
+    "basename *": allow
   webfetch: allow
   websearch: allow
   task:
@@ -43,22 +53,6 @@ You are the **Boomerang Scraper** - web research specialist.
 2. **Fetch pages** - Retrieve and summarize web content
 3. **Synthesize info** - Combine findings into coherent summary
 
-## SCOPE BOUNDARIES
-
-**This agent DOES:**
-- Search the web with searxng
-- Fetch and summarize web pages
-- Synthesize research findings
-- Save valuable research to memini-ai
-
-**This agent DOES NOT:**
-- Edit code (escalate to `boomerang-coder`)
-- Make architecture decisions (escalate to `boomerang-architect`)
-- Write documentation (escalate to `boomerang-writer`)
-- Analyze project code (escalate to `boomerang-architect`)
-
-**When in doubt:** Fetch and return raw findings. Let another agent synthesize into code/docs.
-
 ## Tools
 
 - `searxng_searxng_web_search` - Search the web

package/.opencode/agents/boomerang-tester.md

@@ -25,7 +25,9 @@ permission:
     "webfetch": allow
     "websearch": allow
   edit: allow
-  bash: allow
+  bash:
+    "basename *": allow
+    "*": allow
   task:
     "*": deny
 ---
@@ -40,22 +42,6 @@ You are the **Boomerang Tester** - a testing specialist for boomerang-v3.
 2. **Verify fixes** - Confirm bug fixes with test coverage
 3. **Run test suites** - Execute and interpret test results
 
-## SCOPE BOUNDARIES
-
-**This agent DOES:**
-- Write and run unit/integration tests
-- Verify bug fixes with test coverage
-- Execute and interpret test results
-- Update test infrastructure
-
-**This agent DOES NOT:**
-- Fix production code bugs (escalate to `boomerang-coder`)
-- Make architecture decisions (escalate to `boomerang-architect`)
-- Write non-test code (escalate to `boomerang-coder`)
-- Handle linting/formatting (escalate to `boomerang-linter`)
-
-**When in doubt:** Query memini-ai for previous test patterns in this project.
-
 ## memini-ai Integration
 
 Before writing tests, query memini-ai for:
@@ -65,8 +51,9 @@ Before writing tests, query memini-ai for:
 
 ## Test Commands
 
+**TypeScript** (`boomerang-v3/`):
 ```bash
-# Run tests
+# Run all tests
 cd boomerang-v3 && npm test
 
 # Run specific test file
@@ -74,6 +61,21 @@ npx vitest run tests/[file].test.ts
 
 # Typecheck
 npm run typecheck
+```
+
+**Python** (`memini-ai-dev/`, `boomerang-queue/`, `boomerang-proxy/`):
+```bash
+# Run all tests
+pytest
+
+# Run specific test file
+pytest tests/test_file.py -v
+
+# With coverage
+pytest --cov=src --cov-report=term-missing
+```
+
+**NEVER use `python -c` — always use `uv run` or `uvx` instead.**
 
 # Lint
 npm run lint

package/.opencode/agents/boomerang-writer.md

@@ -27,6 +27,15 @@ permission:
   edit: allow
   bash:
     "ls *": allow
+    "head *": allow
+    "tail *": allow
+    "cat *": allow
+    "grep *": allow
+    "find *": allow
+    "cd *": allow
+    "echo *": allow
+    "which *": allow
+    "basename *": allow
   task:
     "*": deny
 ---
@@ -41,22 +50,6 @@ You are the **Boomerang Writer** - documentation specialist for boomerang-v3.
 2. **Update docs** - Keep docs in sync with code
 3. **Format markdown** - Clean, consistent formatting
 
-## SCOPE BOUNDARIES
-
-**This agent DOES:**
-- Write and update README, API docs, guides
-- Format markdown consistently
-- Keep docs in sync with code changes
-- Create changelogs and release notes
-
-**This agent DOES NOT:**
-- Edit source code (escalate to `boomerang-coder`)
-- Make architecture decisions (escalate to `boomerang-architect`)
-- Write tests (escalate to `boomerang-tester`)
-- Run linting on code (escalate to `boomerang-linter`)
-
-**When in doubt:** Write docs only. Never touch implementation files.
-
 ## memini-ai Integration
 
 Query memini-ai for:

package/.opencode/agents/boomerang.md

@@ -24,19 +24,26 @@ permission:
     "playwright_*": allow
     "webfetch": allow
     "websearch": allow
-  edit: ask
+  edit: allow
   bash:
     "*": ask
     "git *": allow
     "npm *": allow
     "bun *": allow
     "ls *": allow
+    "head *": allow
+    "tail *": allow
     "mkdir *": allow
     "rm *": ask
     "cat *": allow
     "grep *": allow
     "find *": allow
     "cd *": allow
+    "echo *": allow
+    "which *": allow
+    "basename *": allow
+    "chmod *": ask
+    "chown *": ask
   task:
     "*": deny
     "boomerang-coder": allow
@@ -71,37 +78,17 @@ Immediately call `sequential-thinking_sequentialthinking` with your analysis.
 ### STEP 3: Plan (MANDATORY unless explicitly waived)
 Create an implementation plan UNLESS user says "skip planning", "just do it", "/boomerang-handoff", "do a handoff", or "no plan needed".
 
-### STEP 3.5: MANDATORY DISPATCH CHECKLIST (BEFORE DELEGATE)
-Before dispatching ANY task, you MUST verify:
-
-1. [ ] Agent is the CORRECT specialist (see Routing Matrix below)
-2. [ ] `general` is NOT being used for code implementation
-3. [ ] `boomerang-explorer` is NOT being used for research/analysis
-4. [ ] Task scope matches agent's defined scope
-5. [ ] Context Package includes all required fields
-
-### Routing Matrix for Reference
-| Task Type | Primary Agent |
-|-----------|--------------|
-| Code implementation | `boomerang-coder` |
-| Architecture/design | `boomerang-architect` |
-| File finding | `boomerang-explorer` |
-| Testing | `boomerang-tester` |
-| Linting | `boomerang-linter` |
-| Git | `boomerang-git` |
-| Documentation | `boomerang-writer` |
-| Web scraping | `boomerang-scraper` |
-| MCP/debug | `mcp-specialist` |
-| Release | `boomerang-release` |
-
-### ROUTING VIOLATIONS = AUTOMATIC RETRY
-If you dispatch to wrong agent:
-- Cancel incorrect task
-- Re-dispatch to correct agent
-- Save violation to memini-ai for future correction
-
 ### STEP 4: Delegate ALL work via Task tool (MANDATORY)
-You are the ORCHESTRATOR. You CANNOT write code, edit files, or run bash commands.
+
+You are the **ORCHESTRATOR** — your primary job is delegation and coordination. While you CAN edit documentation files (TASKS.md, AGENTS.md, etc.), you should delegate ALL code implementation and testing to specialist sub-agents.
+
+**PARALLEL EXECUTION IS MANDATORY** — Always look for opportunities to dispatch multiple sub-agents simultaneously. Launch tasks in parallel whenever there are no dependencies between them. This maximizes throughput and respects the 3 concurrent slot limit.
+
+Examples of parallel dispatch:
+- Linter + Tester for independent validation tasks
+- Coder + Writer for code + docs
+- Multiple Coders for unrelated file changes
+
 Your only purpose is to delegate to sub-agents using the Task tool.
 
 ## Project-Specific Context

package/.opencode/agents/mcp-specialist.md

@@ -27,6 +27,15 @@ permission:
   edit: allow
   bash:
     "ls *": allow
+    "head *": allow
+    "tail *": allow
+    "cat *": allow
+    "grep *": allow
+    "find *": allow
+    "cd *": allow
+    "echo *": allow
+    "which *": allow
+    "basename *": allow
   task:
     "*": deny
 ---
@@ -41,22 +50,6 @@ You are the **MCP Specialist** - MCP Protocol expert for boomerang-v3.
 2. **Debug servers** - Troubleshoot MCP issues
 3. **Review integrations** - Validate MCP implementations
 
-## SCOPE BOUNDARIES
-
-**This agent DOES:**
-- Design MCP tool schemas
-- Debug MCP server issues
-- Review and validate MCP integrations
-- Document MCP protocols
-
-**This agent DOES NOT:**
-- Edit general application code (escalate to `boomerang-coder`)
-- Make system architecture decisions (escalate to `boomerang-architect`)
-- Write tests for non-MCP code (escalate to `boomerang-tester`)
-- Handle release tasks (escalate to `boomerang-release`)
-
-**When in doubt:** Stay within MCP protocol scope. Query memini-ai for existing MCP patterns.
-
 ## memini-ai Integration
 
 For MCP design:

package/.opencode/agents/researcher.md

@@ -27,6 +27,16 @@ permission:
   edit: deny
   bash:
     "curl *": allow
+    "ls *": allow
+    "head *": allow
+    "tail *": allow
+    "cat *": allow
+    "grep *": allow
+    "find *": allow
+    "cd *": allow
+    "echo *": allow
+    "which *": allow
+    "basename *": allow
   webfetch: allow
   websearch: allow
   task:
@@ -50,22 +60,6 @@ You are the **Researcher** - web research specialist for boomerang-v3.
 - `memini-ai-dev_add_memory` - Save research findings
 - `memini-ai-dev_query_kg` - Query knowledge graph
 
-## SCOPE BOUNDARIES
-
-**This agent DOES:**
-- Search the web with searxng
-- Retrieve and analyze web content
-- Synthesize findings into coherent research
-- Save research to memini-ai with `project` tag
-
-**This agent DOES NOT:**
-- Edit code (escalate to `boomerang-coder`)
-- Make architecture decisions (escalate to `boomerang-architect`)
-- Write documentation (escalate to `boomerang-writer`)
-- Analyze project source code (escalate to `boomerang-architect`)
-
-**When in doubt:** Return research findings. Let another agent act on them.
-
 ## Research Process
 
 1. Query memini-ai for existing knowledge

package/AGENTS.md

@@ -84,21 +84,31 @@ The orchestrator MUST delegate based on these rules. No exceptions.
 
 ### Orchestrator Permissions (v3.0.0)
 
-The orchestrator provides **intelligent routing and context building** — it does not execute agents directly.
+The orchestrator provides **intelligent routing and context building** — it primarily delegates to sub-agents but CAN edit documentation files directly (TASKS.md, AGENTS.md, CONTEXT.md, HANDOFF.md).
 
 **Orchestrator Does:**
 - Analyze request and detect task type
 - Query memini-ai for relevant context
 - Select appropriate agent based on task
 - Build rich Context Package with all necessary information
+- Edit documentation and todo lists directly
 - Return `{agent, systemPrompt, contextPackage, suggestions}` to OpenCode
 
 **Orchestrator Delegates:**
 - Agent execution → OpenCode (native)
+- Code implementation → boomerang-coder
+- Testing → boomerang-tester
+- Linting → boomerang-linter
+- Git operations → boomerang-git
 - Multi-file changes → sub-agents
 - Complex implementation → boomerang-coder
 - Architecture decisions → boomerang-architect
 
+**PARALLEL EXECUTION IS MANDATORY** — The orchestrator MUST launch multiple sub-agents simultaneously when tasks have no dependencies. Examples:
+- Linter + Tester for independent validation
+- Coder + Writer for code + documentation
+- Multiple Coders for unrelated file changes
+
 **Decision Threshold:**
 ```
 Task Size ≤ 1 file AND ≤ 20 lines AND deterministic
@@ -365,7 +375,10 @@ IDLE → MEMORY_QUERY → SEQUENTIAL_THINK → PLAN → DELEGATE → GIT_CHECK
 
 ## Review Notes
 
-- **2026-05-19**: **CRITICAL FIX: Agent Permissions Overhaul** — Changed all 14 specialist agents from `mode: primary` to `mode: subagent` (orchestrator: `mode: all`). Added comprehensive permissions to all 30 agent files (`.opencode/agents/` + `boomerang-v3/.opencode/agents/`): read/glob/grep/list/todowrite/external_directory/lsp/skill/question/doom_loop all `allow`, tool permissions for memini-ai-dev_*, searxng_*, sequential-thinking_*, markitdown_*, github-mcp_*, playwright_*, webfetch, websearch. Per-agent edit/bash/task permissions. Task tool can now properly invoke boomerang-coder, boomerang-architect, boomerang-tester, etc.
+- **2026-05-19**: **boomerang-v3 v0.3.2 UPDATED** — Agent bash permissions expanded: `basename`, `diff`, `cp`, `which` added. Orchestrator clarified: CAN edit docs, delegates code. Parallel execution guidance added. All 30 agent files synced between `.opencode/agents/` and `boomerang-v3/.opencode/agents/`.
+- **2026-05-19**: **boomerang-v3 v0.3.1 RELEASED** — Added common bash commands (ls, head, tail, cat, grep, find, cd, echo) to 7 agent permission files. Tag `v0.3.1` pushed to GitHub.
+- **2026-05-19**: **boomerang-v3 v0.3.0 RELEASED** — Agent permissions overhaul: `mode: subagent` + comprehensive tool permissions for all 30 agent files. SQL injection fix in boomerang-queue. Phase 3 Ollama Cloud Proxy design doc created. Tag `v0.3.0` pushed to GitHub.
+- **2026-05-19**: **memini-ai-dev v0.2.8 RELEASED** — Ruff formatting pass (isort, whitespace, imports) across 30 files. No functional changes. Tag `v0.2.8` pushed to GitHub.
 - **2026-05-19**: Updated to Ollama Cloud models — All agents reassigned to Ollama Cloud models with 3 concurrent limit. Created `.opencode/opencode.json` with `ollama-cloud` provider. Provider ID: `ollama`, baseURL: `https://ollama.com/v1`.
 - **2026-05-18**: v3.0.0 RELEASED — memini-ai integration: Trust engine, knowledge graph, tiered loading. PostgreSQL with pgvector backend. 645 tests passing in memini-ai.
 - **2026-05-06**: v4.1.0 (boomerang-v2) — Protocol enforcement: MANDATORY. Parallel agent launching.

package/dist/concurrency/retry-executor.js

@@ -1,6 +1,7 @@
 /**
  * Retry Executor — Exponential backoff with jitter for transient failures
  */
+import { TimeoutError } from '../types.js';
 function sleep(ms) {
     return new Promise((resolve) => setTimeout(resolve, ms));
 }
@@ -10,7 +11,9 @@ function calculateDelay(attempt, baseDelayMs, maxDelayMs) {
     const jitter = Math.random() * (capped / 2);
     return Math.floor(capped + jitter);
 }
-const DEFAULT_IS_RETRYABLE = () => true;
+const DEFAULT_IS_RETRYABLE = (error) => {
+    return !(error instanceof TimeoutError);
+};
 export async function executeWithRetry(fn, options = {}) {
     const maxRetries = options.maxRetries ?? 3;
     const baseDelayMs = options.baseDelayMs ?? 1000;

package/dist/orchestrator.js

@@ -18,6 +18,7 @@ function validateAgentRouting(taskType, agentName) {
     }
     return true;
 }
+import { TimeoutError } from './types.js';
 import { TaskLimiter, executeWithRetry, executeWithTimeout, } from './concurrency/index.js';
 export class BoomerangOrchestrator {
     taskLimiter;
@@ -64,6 +65,7 @@ export class BoomerangOrchestrator {
                 maxRetries: this.config.maxRetries,
                 baseDelayMs: this.config.retryBaseDelayMs,
                 maxDelayMs: this.config.retryMaxDelayMs,
+                isRetryable: (err) => !(err instanceof TimeoutError),
             });
             return retryResult;
         }

package/docs/CONFIG_RESEARCH.md

@@ -0,0 +1,104 @@
+# OpenCode Feature Evaluation for boomerang-v3
+
+**Date**: 2026-05-19
+**Author**: boomerang-architect (deepseek-v4-pro:cloud)
+**Context**: Evaluating 3 OpenCode features identified in the compliance audit for potential integration into boomerang-v3.
+
+---
+
+## 1. Plugin Hooks
+
+### Summary
+OpenCode plugins support 25+ lifecycle hooks via TypeScript/JS modules in `.opencode/plugins/`. Boomerang-v3 is already loaded as a plugin (`@veedubin/boomerang-v3` in `opencode.json`). Adding hooks is incremental — just export them from the existing plugin structure. Key hooks: `tool.execute.before`, `tool.execute.after`, `experimental.session.compacting`, `session.compacted`, `session.created`, `file.edited`.
+
+### Pros
+- **Compaction hook solves context loss**: `experimental.session.compacting` fires before the LLM compaction prompt is generated, letting us inject boomerang state (task graph, slot usage, queued jobs) that survives context pruning. This directly addresses the context preservation problem from our earlier design work.
+- **Routing validation**: `tool.execute.before` can enforce the mandatory routing matrix (e.g., block `general` from editing code, block `explorer` from doing research).
+- **No new infrastructure**: Already running as a plugin; hooks are just additional exports.
+- **Audit trail**: `tool.execute.after` enables comprehensive tool call logging.
+
+### Cons
+- **`experimental.session.compacting` is unstable API**: The `experimental` prefix means the hook signature may break between OpenCode versions. Requires version-pinning and defensive coding.
+- **Hook ordering undefined**: Multiple plugins' hooks run in load order; we can't guarantee ours runs first.
+- **`tool.execute.before` can't see routing context**: The hook receives raw tool input/output but doesn't have access to the orchestrator's decision state.
+
+### Recommendation: **IMPLEMENT (selectively)**
+
+| Hook | Priority | Use Case |
+|------|----------|----------|
+| `experimental.session.compacting` | HIGH | Inject boomerang state summary before compaction |
+| `tool.execute.before` | HIGH | Validate routing rules |
+| `tool.execute.after` | MEDIUM | Log all tool calls for debugging |
+| `session.created` | LOW | Initialize boomerang session state |
+
+### Effort Estimate
+**4-6 hours** — Add 4 hook exports to existing plugin, test compaction scenarios, verify routing enforcement. ~150 lines of code.
+
+---
+
+## 2. Structured Output (JSON Schema)
+
+### Summary
+The `@opencode-ai/sdk` supports `format: { type: "json_schema", schema, retryCount? }` for enforcing structured JSON output from the model. The model uses a `StructuredOutput` tool that retries on validation failure (default 2 retries). Results are accessible via `result.data.info.structured_output`.
+
+### Pros
+- **Guaranteed structure**: Validated JSON matching a schema, eliminating parsing errors.
+- **SDK-native**: No additional dependencies.
+- **Retry mechanism**: `retryCount` handles transient format failures.
+
+### Cons
+- **Model adherence varies**: We use 10 Ollama Cloud models with different JSON adherence rates. Retry overhead compounds at our scale (15 sub-agents).
+- **Architecture mismatch**: Agent contracts are thin summaries; the rich data (decisions, trade-offs, research) is stored in memini-ai's PostgreSQL backend — already structured.
+- **Schema maintenance burden**: 15 agents × 1 output schema each = 15 schemas to define, version, and update as agents evolve.
+- **Added latency**: Each retry is an additional round-trip to the model. At 2 retries × 60s avg, worst-case adds 2 minutes per agent call.
+- **Markdown convention works**: Our current "## Architectural Plan:" header-based parsing is human-readable and sufficient for orchestrator dispatch.
+
+### Recommendation: **SKIP (revisit Q3 2026)**
+
+The cost-benefit doesn't justify structured output given our architecture. Agent outputs are thin signals; structured data lives in memini-ai. Revisit when Ollama Cloud models have more consistent JSON adherence or when OpenCode adds provider-level structured output enforcement.
+
+### Effort Estimate
+**0 hours now**. If revisited: ~8-10 hours for 15 schemas + validation + retry tuning.
+
+---
+
+## 3. Dynamic MCP Registration (POST /mcp)
+
+### Summary
+OpenCode server exposes `POST /mcp` to dynamically register MCP servers at runtime, accepting `{ name, config }` with the same schema as static `opencode.json` MCP entries. `GET /mcp` returns status for all registered servers.
+
+### Pros
+- **Runtime flexibility**: Could register/unregister MCP servers based on task type.
+- **Health-check integration**: Could auto-restart failed MCP servers.
+- **Auto-detection**: Could probe for `uvx` path and auto-configure `memini-ai-dev`.
+
+### Cons
+- **No current need**: memini-ai-dev is statically configured and working. All 7 MCP servers are stable.
+- **uvx path is stable**: The `uvx --from memini-ai-dev memini-ai --stdio` command hasn't changed. Auto-detection solves a non-problem.
+- **Adds complexity**: Dynamic registration means managing server lifecycle, reconnection logic, and state synchronization — all for servers that never change.
+- **Static config is simpler**: The `opencode.json` approach is declarative, auditable, and version-controlled.
+- **If boomerang-queue goes MCP**: Static config is still the right approach — add it to opencode.json, not register at runtime.
+
+### Recommendation: **SKIP**
+
+No current use case justifies dynamic registration. Static config provides audit trail, version control, and simplicity. The one defensible use case (health-check-driven restart) is a separate concern from registration and would require a health-check plugin, not the `POST /mcp` endpoint.
+
+### Effort Estimate
+**0 hours**. If a use case emerges: ~3-4 hours for registration logic + tests.
+
+---
+
+## Decision Summary
+
+| Feature | Recommendation | Effort | Rationale |
+|---------|---------------|--------|-----------|
+| Plugin Hooks | IMPLEMENT (selectively) | 4-6h | Direct value: compaction context preservation + routing enforcement |
+| Structured Output | SKIP | 0h | Architecture mismatch; rich data already in memini-ai |
+| Dynamic MCP | SKIP | 0h | No use case; static config is simpler and auditable |
+
+### Priority Order
+1. Implement `experimental.session.compacting` hook (context preservation)
+2. Implement `tool.execute.before` hook (routing validation)
+3. Implement `tool.execute.after` hook (audit logging)
+4. Revisit structured output when Ollama Cloud JSON adherence improves
+5. Keep dynamic MCP on watchlist for health-check integration

package/eslint.config.js

@@ -0,0 +1,27 @@
+import js from '@eslint/js';
+import tseslint from 'typescript-eslint';
+
+export default tseslint.config(
+  js.configs.recommended,
+  ...tseslint.configs.recommended,
+  {
+    files: ['src/**/*.ts'],
+    languageOptions: {
+      parser: tseslint.parser,
+      parserOptions: {
+        projectService: true,
+      },
+    },
+    rules: {
+      'no-console': 'warn',
+      'no-unused-vars': 'off',
+      '@typescript-eslint/no-unused-vars': [
+        'error',
+        { argsIgnorePattern: '^_', varsIgnorePattern: '^_' },
+      ],
+    },
+  },
+  {
+    ignores: ['dist/', 'node_modules/', 'coverage/'],
+  }
+);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@veedubin/boomerang-v3",
-  "version": "0.3.0",
+  "version": "0.3.2",
   "description": "Multi-agent orchestration plugin for OpenCode with memini-ai memory",
   "type": "module",
   "main": "dist/index.js",
@@ -25,7 +25,7 @@
     "typecheck": "tsc --noEmit",
     "test": "vitest run",
     "test:watch": "vitest",
-    "lint": "eslint src --ext .ts"
+    "lint": "eslint src"
   },
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.0.0"
@@ -35,6 +35,7 @@
     "@types/node": "^22.0.0",
     "eslint": "^10.4.0",
     "typescript": "^5.7.0",
+    "typescript-eslint": "^8.30.0",
     "vitest": "^3.0.0"
   },
   "engines": {

package/src/concurrency/retry-executor.ts

@@ -3,6 +3,7 @@
  */
 
 import type { RetryOptions, RetryResult } from '../types.js';
+import { TimeoutError } from '../types.js';
 
 function sleep(ms: number): Promise<void> {
   return new Promise((resolve) => setTimeout(resolve, ms));
@@ -15,7 +16,9 @@ function calculateDelay(attempt: number, baseDelayMs: number, maxDelayMs: number
   return Math.floor(capped + jitter);
 }
 
-const DEFAULT_IS_RETRYABLE = (): boolean => true;
+const DEFAULT_IS_RETRYABLE = (error: Error): boolean => {
+  return !(error instanceof TimeoutError);
+};
 
 export async function executeWithRetry<T>(
   fn: () => Promise<T>,

package/src/orchestrator.ts

@@ -34,6 +34,7 @@ import type {
   ConcurrencyConfig,
   SlotUsage,
 } from './types.js';
+import { TimeoutError } from './types.js';
 import {
   TaskLimiter,
   executeWithRetry,
@@ -126,6 +127,7 @@ export class BoomerangOrchestrator {
           maxRetries: this.config.maxRetries,
           baseDelayMs: this.config.retryBaseDelayMs,
           maxDelayMs: this.config.retryMaxDelayMs,
+          isRetryable: (err) => !(err instanceof TimeoutError),
         }
       );
       return retryResult;