@reinamaccredy/oh-my-opencode 3.0.0-beta.14 → 3.0.0-beta.15

package/dist/index.js

@@ -16974,13 +16974,7 @@ var GOOGLE_TO_PROXYPAL_MODEL_MAP = {
   "google/gemini-3-pro-high": "proxypal/gemini-3-pro-preview",
   "google/gemini-3-pro-low": "proxypal/gemini-3-pro-preview"
 };
-var MODEL_TO_CATEGORY_MAP = {
-  "proxypal/gemini-3-pro-preview": "visual-engineering",
-  "proxypal/gpt-5.2-codex": "ultrabrain",
-  "proxypal/gemini-3-flash-preview": "quick",
-  "proxypal/gemini-claude-opus-4-5-thinking": "most-capable",
-  "proxypal/gemini-claude-sonnet-4-5-thinking": "general"
-};
+var MODEL_TO_CATEGORY_MAP = {};
 function migrateGoogleToProxypalModel(model) {
   const proxypalModel = GOOGLE_TO_PROXYPAL_MODEL_MAP[model];
   if (proxypalModel) {
@@ -19274,8 +19268,32 @@ function createBackgroundNotificationHook(manager) {
   const eventHandler = async ({ event }) => {
     manager.handleEvent(event);
   };
+  const toolExecuteAfterHandler = async (input, output) => {
+    const sessionID = input.sessionID;
+    if (!sessionID)
+      return;
+    if (!manager.hasPendingNotifications(sessionID))
+      return;
+    const notifications = manager.consumePendingNotifications(sessionID);
+    if (notifications.length === 0)
+      return;
+    const messages = notifications.map((n) => {
+      if (n.status === "error") {
+        return `[BACKGROUND TASK FAILED] Task "${n.description}" failed after ${n.duration}. Error: ${n.error || "Unknown error"}. Use background_output with task_id="${n.taskId}" for details.`;
+      }
+      return `[BACKGROUND TASK COMPLETED] Task "${n.description}" finished in ${n.duration}. Use background_output with task_id="${n.taskId}" to get results.`;
+    });
+    const injection = `
+
+---
+` + messages.join(`
+`) + `
+---`;
+    output.output = output.output + injection;
+  };
   return {
-    event: eventHandler
+    event: eventHandler,
+    "tool.execute.after": toolExecuteAfterHandler
   };
 }
 // src/hooks/auto-update-checker/checker.ts
@@ -21295,397 +21313,219 @@ function mergeSkills(builtinSkills, config, userClaudeSkills, userOpencodeSkills
   }
   return Array.from(skillMap.values());
 }
-// src/features/builtin-skills/skills.ts
-var maestroCoreSkill = {
-  name: "maestro-core",
-  description: "Use when any Maestro skill loads - provides skill hierarchy, HALT/DEGRADE policies, and trigger routing rules for orchestration decisions",
-  template: `# Maestro Core - Workflow Router
-
-Central hub for Maestro workflow skills. Routes triggers, defines hierarchy, and handles fallbacks.
+// src/features/maestro/skills/index.ts
+var tddSkill = {
+  name: "tdd",
+  description: "TDD methodology for implementation tasks. Enforces RED\u2192GREEN\u2192REFACTOR cycle. Auto-injected for ci/co/ca modes.",
+  template: `# TDD - Test-Driven Development
 
-## Skill Hierarchy
+Enforce RED \u2192 GREEN \u2192 REFACTOR cycle for all implementation work.
 
-\`\`\`
-conductor (1) > orchestrator (2) > designing (3) > tracking (4) > specialized (5)
-\`\`\`
-
-Higher rank wins on conflicts.
-
-## Ownership Matrix
+## Cycle
 
-| Skill | Owns | Primary Triggers |
-|-------|------|------------------|
-| conductor | Implementation + autonomous | \`ci\`, \`ca\`, \`/conductor-implement\`, \`/conductor-autonomous\` |
-| orchestrator | Parallel execution | \`co\`, \`/conductor-orchestrate\` |
-| designing | Phases 1-10 (design \u2192 track creation) | \`ds\`, \`cn\`, \`/conductor-newtrack\`, \`/conductor-design\` |
-| tracking | Task/bead management | \`bd *\`, \`fb\`, \`rb\` |
-| handoff | Session cycling | \`ho\`, \`/conductor-finish\`, \`/conductor-handoff\` |
-| creating-skills | Skill authoring | "create skill", "write skill" |
+| Phase | Action | Gate |
+|-------|--------|------|
+| RED | Write failing test first | Test must FAIL |
+| GREEN | Implement minimal code to pass | Test must PASS |
+| REFACTOR | Clean up while tests pass | All tests PASS |
 
-## Workflow Chain
-
-\`\`\`
-ds/cn \u2192 design.md \u2192 /conductor-newtrack \u2192 spec.md + plan.md \u2192 fb \u2192 tracking \u2192 ci/co/ca \u2192 implementation
-\`\`\`
+## Protocol
 
-## Routing Table
+1. **Before implementation**: Write test that captures expected behavior
+2. **Run test**: Verify it fails for the right reason
+3. **Implement**: Write minimal code to make test pass
+4. **Verify**: Run test, must pass
+5. **Refactor**: Clean up code, run tests after each change
+6. **Repeat**: Next behavior/requirement
 
-**CRITICAL:** After loading \`maestro-core\`, you MUST explicitly load the target skill via \`skill(name="...")\` before proceeding.
+## Commands
 
-### Quick Triggers
-
-| Trigger | Skill |
-|---------|-------|
-| \`ds\`, \`cn\` | designing |
-| \`ci\` | conductor |
-| \`ca\` | conductor |
-| \`co\` | orchestrator |
-| \`fb\`, \`rb\`, \`bd *\` | tracking |
-| \`ho\` | handoff |
+\`\`\`bash
+# Run tests (detect project type)
+bun test || npm test || pnpm test || yarn test
 
-### Routing Flow
+# Run specific test file
+bun test {file} || npm test -- {file}
 
-\`\`\`
-1. User triggers command (e.g., \`ci\`)
-2. Load maestro-core \u2192 get routing table
-3. Look up trigger \u2192 find target skill
-4. MUST call skill tool to load target skill
-5. Follow loaded skill instructions
+# Watch mode (if supported)
+bun test --watch || npm test -- --watch
 \`\`\`
 
-## Fallback Policies
+## Gate Rules
 
-| Condition | Action | Message |
-|-----------|--------|---------|
-| \`bd\` unavailable | HALT | \`\u274C Cannot proceed: bd CLI required\` |
-| \`conductor/\` missing | DEGRADE | \`\u26A0\uFE0F Standalone mode - limited features\` |
-| Agent Mail unavailable | HALT | \`\u274C Cannot proceed: Agent Mail required for coordination\` |
+- Cannot mark task complete if tests fail
+- Cannot skip RED phase (write test first)
+- Cannot proceed to next task with failing tests
+- Must run tests after REFACTOR
 
-## Related Skills
+## Anti-Patterns
 
-- **designing** - Double Diamond design sessions (phases 1-10)
-- **conductor** - Implementation execution
-- **orchestrator** - Multi-agent parallel execution
-- **tracking** - Issue tracking and dependency graphs
-- **handoff** - Session cycling and context preservation`
+- Writing implementation before test (violates RED)
+- Writing more code than needed to pass (violates GREEN)
+- Skipping REFACTOR phase
+- Ignoring test failures`
 };
-var designingSkill = {
-  name: "designing",
-  description: 'Design Session - collaborative brainstorming to turn ideas into actionable implementation plans using the Unified Pipeline methodology. Use when user types "ds" or wants to explore/design a feature before implementation. "pl" triggers phases 5-10 (STANDALONE/ALIAS/NO-OP modes). MUST load maestro-core skill first for routing.',
-  template: `# Design & Planning
-
-Turn ideas into fully-formed, implementation-ready designs through a unified 10-phase pipeline.
-
-## Entry Points
-
-| Trigger | Action |
-|---------|--------|
-| \`ds\` | Start unified pipeline (all 10 phases) |
-| \`/conductor-design\` | Start unified pipeline (alias) |
-| \`cn\`, \`/conductor-newtrack\` | Create spec + plan + beads from existing design.md |
-| \`pl\`, \`/plan\` | Planning phases (5-10) - see pl Entry Modes below |
-| "design a feature" | Start unified pipeline |
-| "let's think through X" | Start unified pipeline |
-
-## Quick Reference
-
-### Unified Pipeline (10 Phases)
+var agentMailSkill = {
+  name: "agent-mail",
+  description: "Worker coordination for parallel execution. Provides messaging, file reservations, and session management. Auto-injected for co/ca modes.",
+  template: `# Agent Mail - Worker Coordination
 
-| # | Phase | Type | Purpose | Exit Criteria |
-|---|-------|------|---------|---------------|
-| 1 | **DISCOVER** | Diverge | Explore problem + research context | Problem articulated |
-| 2 | **DEFINE** | Converge | Frame problem + select approach | Approach selected |
-| 3 | **DEVELOP** | Diverge | Architecture + components | Interfaces defined |
-| 4 | **VERIFY** | Converge | Oracle audit + risk assessment | Oracle APPROVED |
-| 5 | **DECOMPOSE** | Execute | Create beads (fb) | Beads filed |
-| 6 | **VALIDATE** | Execute | Dependency check (bv) + Oracle review | Dependencies valid |
-| 7 | **ASSIGN** | Execute | Track assignments | Tracks assigned |
-| 8 | **READY** | Complete | Handoff to ci/co/ca | Execution ready |
-| 9 | **EXECUTE** | Implement | Run ci/co/ca on tracks | All beads completed |
-| 10 | **FINISH** | Archive | Extract learnings + archive track | Track archived |
+CLI-based coordination for parallel workers in co/ca modes.
 
-## Mode Routing
+## CLI Location
 
-Complexity scoring determines execution mode:
-
-| Score | Mode | Phases | A/P/C | Research |
-|-------|------|--------|-------|----------|
-| < 4 | **SPEED** | 1,2,4,8 | No | 1 hook (start) |
-| 4-6 | **ASK** | User chooses | Optional | User chooses |
-| > 6 | **FULL** | 1-10 | Yes | 2 hooks |
-
-## Core Principles
+\`\`\`bash
+bun toolboxes/agent-mail/agent-mail.js <command>
+\`\`\`
 
-- **One question at a time** - Don't overwhelm
-- **Multiple choice preferred** - Easier to answer
-- **YAGNI ruthlessly** - Remove unnecessary features
-- **Explore alternatives** - Always propose 2-3 approaches
-- **Research consolidated** - 2 strategic hooks, not 5
+## Worker 4-Step Protocol
 
-## \u26D4 EXECUTION BLOCKS (CRITICAL)
+| Step | Command | Required |
+|------|---------|----------|
+| 1. INIT | \`macro-start-session\` | FIRST |
+| 2. WORK | (do assigned tasks) | - |
+| 3. REPORT | \`send-message\` | LAST |
+| 4. CLEANUP | \`release-file-reservations\` | LAST |
 
-**This skill contains EXECUTION BLOCKS marked with \u26D4. When you encounter one, you MUST:**
-1. **STOP** what you're doing
-2. **EXECUTE** the tool calls specified (Task(), oracle(), skill())
-3. **WAIT** for results before proceeding
+## Commands
 
-**EXECUTION BLOCKS are NOT documentation - they are COMMANDS you must execute.**
+### Session Management
+\`\`\`bash
+# Initialize worker session
+bun toolboxes/agent-mail/agent-mail.js macro-start-session
 
-## Session Flow
+# Health check
+bun toolboxes/agent-mail/agent-mail.js health-check
+\`\`\`
 
-0. **Load Core** - Load maestro-core for routing table and fallback policies
-1. **Initialize** - Load handoffs, CODEMAPS, verify conductor setup
-2. **Research** - \u26D4 EXECUTION BLOCK at Phase 1 start (spawn 3 Task() agents)
-3. **Route** - Score complexity (< 4 = SPEED, > 6 = FULL)
-4. **Execute** - 10-phase pipeline with A/P/C checkpoints
-5. **Validate** - \u26D4 EXECUTION BLOCK at Phase 4 (call oracle())
-6. **Complete** - Phase 8 (READY) triggers \`ci\`/\`co\`/\`ca\` \u2192 Phase 9 (EXECUTE) \u2192 Phase 10 (FINISH)
+### Messaging
+\`\`\`bash
+# Send message to orchestrator
+bun toolboxes/agent-mail/agent-mail.js send-message --to orchestrator --body "Epic complete"
 
-## Next Steps (after Phase 8: READY)
+# Check inbox for blockers/instructions
+bun toolboxes/agent-mail/agent-mail.js fetch-inbox
 
-| Command | Description | Phase |
-|---------|-------------|-------|
-| \`ci\` | \`/conductor-implement\` - Execute track | Phase 9 (EXECUTE) |
-| \`co\` | \`/conductor-orchestrate\` - Spawn parallel workers | Phase 9 (EXECUTE) |
-| \`ca\` | \`/conductor-autonomous\` - Ralph loop | Phase 9 (EXECUTE) |
-| \`/conductor-finish\` | Archive track + extract learnings | Phase 10 (FINISH) |
+# Reply to message
+bun toolboxes/agent-mail/agent-mail.js reply-message --id <msg-id> --body "Acknowledged"
+\`\`\`
 
-## Anti-Patterns
+### File Reservations
+\`\`\`bash
+# Reserve files before editing
+bun toolboxes/agent-mail/agent-mail.js reserve-files --paths "src/api/user.ts,src/api/auth.ts"
 
-- \u274C Jumping to solutions before understanding the problem
-- \u274C Skipping verification at Phase 4 (VERIFY)
-- \u274C Asking multiple questions at once
-- \u274C Over-engineering simple features (use SPEED mode)
-- \u274C Running \`pl\` after \`ds\` completes (no longer needed)
+# Release reservations when done
+bun toolboxes/agent-mail/agent-mail.js release-file-reservations
+\`\`\`
 
-## Related
+## Rules
 
-- **conductor** - Track creation and implementation
-- **tracking** - Issue tracking after design
-- **orchestrator** - Parallel execution in Phase 9 (EXECUTE)`
+- Never start work before \`macro-start-session\`
+- Never exit without \`send-message\` to orchestrator
+- Never touch files outside assigned scope
+- Always release reservations on completion
+- Report blockers immediately via \`send-message\``
 };
+function createMaestroSkills() {
+  return [tddSkill, agentMailSkill];
+}
+
+// src/features/builtin-skills/skills.ts
 var conductorSkill = {
   name: "conductor",
-  description: "Implementation execution for context-driven development. Trigger with ci, /conductor-implement, or /conductor-* commands. Use when executing tracks with specs/plans. For design phases, see designing skill. For session handoffs, see handoff skill.",
+  description: "Implementation execution with TDD. Trigger with ci (sequential), co (parallel), or ca (autonomous). Auto-injects tdd skill for all modes, agent-mail for co/ca.",
   template: `# Conductor: Implementation Execution
 
-Execute tracks with TDD and parallel routing.
+Execute implementation with TDD and optional parallel routing.
 
 ## Entry Points
 
-| Trigger | Action | Reference |
-|---------|--------|-----------|
-| \`/conductor-setup\` | Initialize project context | Setup workflow |
-| \`/conductor-implement\` | Execute track (auto-routes if parallel) | Implement workflow |
-| \`ca\`, \`/conductor-autonomous\` | **Run ralph.sh directly** (no Task/sub-agents) | Autonomous workflow |
-| \`/conductor-status\` | Display progress overview | Structure |
-| \`/conductor-revise\` | Update spec/plan mid-work | Revisions |
-
-## Related Skills (Not Owned by Conductor)
-
-| For... | Use Skill | Triggers |
-|--------|-----------|----------|
-| Design phases (1-8) | designing | \`ds\`, \`cn\`, \`/conductor-design\`, \`/conductor-newtrack\` |
-| Session handoffs | handoff | \`ho\`, \`/conductor-finish\`, \`/conductor-handoff\` |
+| Trigger | Mode | Description |
+|---------|------|-------------|
+| \`ci\` | Sequential | Execute beads one-by-one with TDD |
+| \`co\` | Parallel | Spawn workers per epic, coordinate via Agent Mail |
+| \`ca\` | Autonomous | Ralph loop - continuous execution until complete |
 
-## Quick Reference
-
-| Phase | Purpose | Output | Skill |
-|-------|---------|--------|-------|
-| Requirements | Understand problem | design.md | designing |
-| Plan | Create spec + plan | spec.md + plan.md | designing |
-| **Implement** | Build with TDD | Code + tests | **conductor** |
-| **Autonomous** | Ralph loop execution | Auto-verified stories | **conductor** |
-| Reflect | Verify before shipping | LEARNINGS.md | handoff |
-
-## Core Principles
-
-- **Load core first** - Load maestro-core for routing table and fallback policies
-- **TDD by default** - RED \u2192 GREEN \u2192 REFACTOR (use \`--no-tdd\` to disable)
-- **Beads integration** - Zero manual \`bd\` commands in happy path
-- **Parallel routing** - \`## Track Assignments\` in plan.md triggers orchestrator
-- **Validation gates** - Automatic checks at each phase transition
-
-## Directory Structure
-
-\`\`\`
-conductor/
-\u251C\u2500\u2500 product.md, tech-stack.md, workflow.md  # Project context
-\u251C\u2500\u2500 code_styleguides/                       # Language-specific style rules
-\u251C\u2500\u2500 CODEMAPS/                               # Architecture docs
-\u251C\u2500\u2500 handoffs/                               # Session context
-\u251C\u2500\u2500 spikes/                                 # Research spikes (pl output)
-\u2514\u2500\u2500 tracks/<track_id>/                      # Per-track work
-    \u251C\u2500\u2500 design.md, spec.md, plan.md         # Planning artifacts
-    \u2514\u2500\u2500 metadata.json                       # State tracking (includes planning state)
-\`\`\`
-
-## Beads Integration
-
-All execution routes through orchestrator with Agent Mail coordination:
-- Workers claim beads via \`bd update --status in_progress\`
-- Workers close beads via \`bd close --reason completed|skipped|blocked\`
-- File reservations via \`file_reservation_paths\`
-- Communication via \`send_message\`/\`fetch_inbox\`
-
-## /conductor-implement Auto-Routing
-
-1. Read \`metadata.json\` - check \`orchestrated\` flag
-2. Read \`plan.md\` - check for \`## Track Assignments\`
-3. Check \`beads.fileScopes\` - file-scope based grouping
-4. If parallel detected (\u22652 non-overlapping groups) \u2192 Load orchestrator skill
-5. Else \u2192 Sequential execution with TDD
+## Auto-Injected Skills
 
-## Anti-Patterns
-
-- \u274C Manual \`bd\` commands when workflow commands exist
-- \u274C Ignoring validation gate failures
-- \u274C Using conductor for design (use designing instead)
-- \u274C Using conductor for handoffs (use handoff instead)
-
-## Related
-
-- **designing** - Double Diamond design + track creation
-- **handoff** - Session cycling and finish workflow
-- **tracking** - Issue tracking (beads)
-- **orchestrator** - Parallel execution
-- **maestro-core** - Routing policies`
-};
-var orchestratorSkill = {
-  name: "orchestrator",
-  description: 'Multi-agent parallel execution with autonomous workers. Use when plan.md has Track Assignments section or user triggers /conductor-orchestrate, "run parallel", "spawn workers". MUST load maestro-core skill first for routing.',
-  template: `# Orchestrator - Multi-Agent Parallel Execution
-
-> **Spawn autonomous workers to execute tracks in parallel using Agent Mail coordination.**
+| Mode | Skills |
+|------|--------|
+| \`ci\` | tdd, tracking |
+| \`co\` | tdd, agent-mail, tracking |
+| \`ca\` | tdd, agent-mail, tracking |
 
-## Agent Mail: CLI Primary, MCP Fallback
+## TDD Protocol (All Modes)
 
-This skill uses a **lazy-load pattern** for Agent Mail:
+| Phase | Action | Gate |
+|-------|--------|------|
+| RED | Write failing test first | Test must FAIL |
+| GREEN | Implement minimal code | Test must PASS |
+| REFACTOR | Clean up, tests pass | All tests PASS |
 
-| Priority | Tool | When Available |
-|----------|------|----------------|
-| **Primary** | \`bun toolboxes/agent-mail/agent-mail.js\` | Always (via Bash) |
-| **Fallback** | MCP tools (via \`mcp.json\`) | When skill loaded + MCP server running |
+## Sequential Mode (ci)
 
-**Detection flow:**
 \`\`\`
-1. Try CLI: bun toolboxes/agent-mail/agent-mail.js health-check
-   \u2193 success? \u2192 Use CLI for all Agent Mail operations
-   \u2193 fails?
-2. Fallback: MCP tools (lazy-loaded via skills/orchestrator/mcp.json)
+1. bd ready --limit 1          # Get next ready bead
+2. bd update {id} --status in_progress
+3. TDD cycle (RED \u2192 GREEN \u2192 REFACTOR)
+4. bd close {id} --reason completed
+5. Repeat until no ready beads
 \`\`\`
 
-**CLI benefits:** Zero token cost until used, no MCP server dependency.
-
-## Core Principles
-
-- **Load core first** - Load maestro-core for routing table and fallback policies
-- **CLI first** - Use \`bun toolboxes/agent-mail/agent-mail.js\` CLI before falling back to MCP tools
-- **Pre-register workers** before spawning (Agent Mail validates recipients)
-- **Workers own their beads** - can \`bd claim/close\` directly (unlike sequential mode)
-- **File reservations prevent conflicts** - reserve before edit, release on complete
-- **Summary before exit** - all workers MUST send completion message
-- **TDD by default** - workers follow RED \u2192 GREEN \u2192 REFACTOR cycle (use \`--no-tdd\` to disable)
-
-## When to Use
-
-| Trigger | Condition |
-|---------|-----------| 
-| Auto-routed | \`/conductor-implement\` when plan has Track Assignments |
-| File-scope | \`/conductor-implement\` when \u22652 non-overlapping file groups detected |
-| Direct | \`/conductor-orchestrate\` or \`co\` |
-| Phrase | "run parallel", "spawn workers", "dispatch agents" |
-| **See also** | \`ca\` for autonomous execution |
-
-## Auto-Trigger Behavior
-
-Parallel execution starts **automatically** when detected - no confirmation needed:
+## Parallel Mode (co)
 
 \`\`\`
-\uD83D\uDCCA Parallel execution detected:
-- Track A: 2 tasks (src/api/)
-- Track B: 2 tasks (lib/)
-- Track C: 1 task (schemas/)
-
-\u26A1 Spawning workers...
+1. Group ready beads by epic
+2. For each epic, spawn worker:
+   sisyphus_task(
+     category="general",
+     skills=["tdd", "agent-mail", "tracking"],
+     run_in_background=true,
+     prompt="Epic: {title}..."
+   )
+3. Monitor via background_output()
+4. Close epics when all beads complete
 \`\`\`
 
-## Quick Reference
-
-| Action | Tool |
-|--------|------|
-| Parse plan.md | \`Read("conductor/tracks/<id>/plan.md")\` |
-| Initialize | \`bun toolboxes/agent-mail/agent-mail.js macro-start-session\` |
-| Spawn workers | \`Task()\` for each track |
-| Monitor | \`bun toolboxes/agent-mail/agent-mail.js fetch-inbox\` |
-| Resolve blockers | \`bun toolboxes/agent-mail/agent-mail.js reply-message\` |
-| Complete | \`bun toolboxes/agent-mail/agent-mail.js send-message\`, \`bd close epic\` |
-| Track threads | \`bun toolboxes/agent-mail/agent-mail.js summarize-thread\` |
-| Auto-routing | Auto-detect parallel via \`metadata.json.beads\` |
-
-## 8-Phase Orchestrator Protocol
-
-0. **Preflight** - Session identity, detect active sessions
-1. **Read Plan** - Parse Track Assignments from plan.md
-2. **Validate** - Health check Agent Mail CLI (HALT if unavailable)
-3. **Initialize** - ensure_project, register orchestrator + all workers
-4. **Spawn Workers** - Task() for each track (parallel)
-5. **Monitor + Verify** - fetch_inbox, verify worker summaries
-   - Workers use track threads (\`TRACK_THREAD\`) for bead-to-bead context
-6. **Resolve** - reply_message for blockers
-7. **Complete** - Send summary, close epic, \`rb\` review
-
-## Worker 4-Step Protocol
-
-All workers MUST follow this exact sequence:
+## Autonomous Mode (ca)
 
 \`\`\`
-\u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510
-\u2502  STEP 1: INITIALIZE  - bun toolboxes/agent-mail/agent-mail.js macro-start-session   \u2502
-\u2502  STEP 2: EXECUTE     - claim beads, do work, close beads                            \u2502
-\u2502  STEP 3: REPORT      - bun toolboxes/agent-mail/agent-mail.js send-message          \u2502
-\u2502  STEP 4: CLEANUP     - bun toolboxes/agent-mail/agent-mail.js release-file-reservations \u2502
-\u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518
+1. Loop while bd ready shows pending beads:
+   a. Group ready beads by epic
+   b. Spawn parallel workers (like co mode)
+   c. Wait for all workers
+   d. TDD gate check - fix failures
+   e. Continue to next iteration
+2. Exit when all beads complete
 \`\`\`
 
-| Step | Tool | Required |
-|------|------|----------|
-| 1 | \`bun toolboxes/agent-mail/agent-mail.js macro-start-session\` | \u2705 FIRST |
-| 2 | \`bd update\`, \`bd close\` | \u2705 |
-| 3 | \`bun toolboxes/agent-mail/agent-mail.js send-message\` | \u2705 LAST |
-| 4 | \`bun toolboxes/agent-mail/agent-mail.js release-file-reservations\` | \u2705 |
+## Beads Integration
 
-**Critical rules:**
-- \u274C Never start work before \`macro-start-session\`
-- \u274C Never return without \`send-message\` to orchestrator
-- \u274C Never touch files outside assigned scope
+- Claim: \`bd update {id} --status in_progress\`
+- Close: \`bd close {id} --reason completed|skipped|blocked\`
+- Ready: \`bd ready\` shows next available work
 
 ## Anti-Patterns
 
-| \u274C Don't | \u2705 Do |
-|----------|-------|
-| Spawn workers without pre-registration | Register all workers BEFORE spawning |
-| Skip completion summary | Always send_message before exit |
-| Ignore file reservation conflicts | Wait or resolve before proceeding |
-| Use orchestration for simple tasks | Use sequential \`/conductor-implement\` |
+- \u274C Skipping TDD (write test first!)
+- \u274C Not closing beads after completion
+- \u274C Manual orchestration in ci mode (use co instead)
+- \u274C Ignoring test failures
 
 ## Related
 
-- **maestro-core** - Routing and fallback policies
-- **conductor** - Track management, \`/conductor-implement\`
-- **tracking** - Issue tracking, \`bd\` commands`
+- **tdd** - Test-driven development (auto-injected)
+- **agent-mail** - Worker coordination for co/ca (auto-injected)
+- **tracking** - Beads CLI for task management`
 };
 var trackingSkill = {
   name: "tracking",
-  description: `Tracks complex, multi-session work using the Beads issue tracker and dependency graphs, and provides persistent memory that survives conversation compaction. Use when work spans multiple sessions, has complex dependencies, or needs persistent context across compaction cycles. Trigger with phrases like "create task for", "what's ready to work on", "show task", "track this work", "what's blocking", or "update status". MUST load maestro-core skill first for routing.`,
+  description: `Tracks complex, multi-session work using the Beads issue tracker and dependency graphs, and provides persistent memory that survives conversation compaction. Use when work spans multiple sessions, has complex dependencies, or needs persistent context across compaction cycles. Trigger with phrases like "create task for", "what's ready to work on", "show task", "track this work", "what's blocking", or "update status".`,
   template: `# Tracking - Persistent Memory for AI Agents
 
 Graph-based issue tracker that survives conversation compaction. Provides persistent memory for multi-session work with complex dependencies.
 
-## Prerequisites
-
-- **Load maestro-core first** - For routing table and fallback policies
-
 ## Entry Points
 
 | Trigger | Reference | Action |
@@ -21732,9 +21572,7 @@ Graph-based issue tracker that survives conversation compaction. Provides persis
 
 ## Related
 
-- **maestro-core** - Workflow router and skill hierarchy
-- **conductor** - Automated beads operations via facade
-- **orchestrator** - Multi-agent parallel execution`
+- **conductor** - Automated beads operations via ci/co/ca`
 };
 var playwrightSkill = {
   name: "playwright",
@@ -22088,36 +21926,7 @@ CORRECT: Split by directory/concern:
   = 5 commits from 8 files (CORRECT)
 \`\`\`
 
-### 3.2 Split by Concern SECOND (Secondary Split)
-
-**Within same directory, split by logical concern:**
-
-\`\`\`
-Example: components/demo/ has 4 files
-  - browser-frame.tsx (UI frame)
-  - shopify-full-site.tsx (specific demo)
-  - review-dashboard.tsx (NEW - specific demo)
-  - tone-settings.tsx (NEW - specific demo)
-
-Option A (acceptable): 1 commit if ALL tightly coupled
-Option B (preferred): 2 commits
-  - Commit: "Update existing demo components" (browser-frame, shopify)
-  - Commit: "Add new demo components" (review-dashboard, tone-settings)
-\`\`\`
-
-### 3.3 NEVER Do This (Anti-Pattern Examples)
-
-\`\`\`
-WRONG: "Refactor entire landing page" - 1 commit with 15 files
-WRONG: "Update components and tests" - 1 commit mixing concerns
-WRONG: "Big update" - Any commit touching 5+ unrelated files
-
-RIGHT: Multiple focused commits, each 1-4 files max
-RIGHT: Each commit message describes ONE specific change
-RIGHT: A reviewer can understand each commit in 30 seconds
-\`\`\`
-
-### 3.4 Implementation + Test Pairing (MANDATORY)
+### 3.2 Implementation + Test Pairing (MANDATORY)
 
 \`\`\`
 RULE: Test files MUST be in same commit as implementation
@@ -22131,34 +21940,7 @@ Test patterns to match:
 - tests/*.py <-> src/*.py
 \`\`\`
 
-### 3.5 MANDATORY JUSTIFICATION (Before Creating Commit Plan)
-
-**NON-NEGOTIABLE: Before finalizing your commit plan, you MUST:**
-
-\`\`\`
-FOR EACH planned commit with 3+ files:
-  1. List all files in this commit
-  2. Write ONE sentence explaining why they MUST be together
-  3. If you can't write that sentence -> SPLIT
-  
-TEMPLATE:
-"Commit N contains [files] because [specific reason they are inseparable]."
-
-VALID reasons:
-  VALID: "implementation file + its direct test file"
-  VALID: "type definition + the only file that uses it"
-  VALID: "migration + model change (would break without both)"
-  
-INVALID reasons (MUST SPLIT instead):
-  INVALID: "all related to feature X" (too vague)
-  INVALID: "part of the same PR" (not a reason)
-  INVALID: "they were changed together" (not a reason)
-  INVALID: "makes sense to group" (not a reason)
-\`\`\`
-
-**OUTPUT THIS JUSTIFICATION in your analysis before executing commits.**
-
-### 3.7 Dependency Ordering
+### 3.3 Dependency Ordering
 
 \`\`\`
 Level 0: Utilities, constants, type definitions
@@ -22170,22 +21952,7 @@ Level 4: Configuration, infrastructure
 COMMIT ORDER: Level 0 -> Level 1 -> Level 2 -> Level 3 -> Level 4
 \`\`\`
 
-### 3.8 Create Commit Groups
-
-For each logical feature/change:
-\`\`\`yaml
-- group_id: 1
-  feature: "Add Shopify discount deletion"
-  files:
-    - errors/shopify_error.py
-    - types/delete_input.py
-    - mutations/update_contract.py
-    - tests/test_update_contract.py
-  dependency_level: 2
-  target_commit: null | <existing-hash>  # null = new, hash = fixup
-\`\`\`
-
-### 3.9 MANDATORY OUTPUT (BLOCKING)
+### 3.4 MANDATORY OUTPUT (BLOCKING)
 
 **You MUST output this block before proceeding to Phase 4. NO EXCEPTIONS.**
 
@@ -22206,789 +21973,50 @@ COMMIT 2: [message in detected style]
   - path/to/file2.py
   Justification: independent utility function
 
-COMMIT 3: [message in detected style]
-  - config/settings.py
-  - config/constants.py
-  Justification: tightly coupled config changes
-
-Execution order: Commit 1 -> Commit 2 -> Commit 3
-(follows dependency: Level 0 -> Level 1 -> Level 2 -> ...)
+Execution order: Commit 1 -> Commit 2 -> ...
 \`\`\`
-
-**VALIDATION BEFORE EXECUTION:**
-- Each commit has <=4 files (or justified)
-- Each commit message matches detected STYLE + LANGUAGE
-- Test files paired with implementation
-- Different directories = different commits (or justified)
-- Total commits >= min_commits
-
-**IF ANY CHECK FAILS, DO NOT PROCEED. REPLAN.**
 </atomic_planning>
 
 ---
 
-## PHASE 4: Commit Strategy Decision
-
-<strategy_decision>
-### 4.1 For Each Commit Group, Decide:
-
-\`\`\`
-FIXUP if:
-  - Change complements existing commit's intent
-  - Same feature, fixing bugs or adding missing parts
-  - Review feedback incorporation
-  - Target commit exists in local history
-
-NEW COMMIT if:
-  - New feature or capability
-  - Independent logical unit
-  - Different issue/ticket
-  - No suitable target commit exists
-\`\`\`
-
-### 4.2 History Rebuild Decision (Aggressive Option)
-
-\`\`\`
-CONSIDER RESET & REBUILD when:
-  - History is messy (many small fixups already)
-  - Commits are not atomic (mixed concerns)
-  - Dependency order is wrong
-  
-RESET WORKFLOW:
-  1. git reset --soft $(git merge-base HEAD main)
-  2. All changes now staged
-  3. Re-commit in proper atomic units
-  4. Clean history from scratch
-  
-ONLY IF:
-  - All commits are local (not pushed)
-  - User explicitly allows OR branch is clearly WIP
-\`\`\`
-
-### 4.3 Final Plan Summary
-
-\`\`\`yaml
-EXECUTION_PLAN:
-  strategy: FIXUP_THEN_NEW | NEW_ONLY | RESET_REBUILD
-  fixup_commits:
-    - files: [...]
-      target: <hash>
-  new_commits:
-    - files: [...]
-      message: "..."
-      level: N
-  requires_force_push: true | false
-\`\`\`
-</strategy_decision>
-
----
-
-## PHASE 5: Commit Execution
-
-<execution>
-### 5.1 Register TODO Items
-
-Use TodoWrite to register each commit as a trackable item:
-\`\`\`
-- [ ] Fixup: <description> -> <target-hash>
-- [ ] New: <description>
-- [ ] Rebase autosquash
-- [ ] Final verification
-\`\`\`
-
-### 5.2 Fixup Commits (If Any)
-
-\`\`\`bash
-# Stage files for each fixup
-git add <files>
-git commit --fixup=<target-hash>
-
-# Repeat for all fixups...
-
-# Single autosquash rebase at the end
-MERGE_BASE=$(git merge-base HEAD main 2>/dev/null || git merge-base HEAD master)
-GIT_SEQUENCE_EDITOR=: git rebase -i --autosquash $MERGE_BASE
-\`\`\`
-
-### 5.3 New Commits (After Fixups)
-
-For each new commit group, in dependency order:
-
-\`\`\`bash
-# Stage files
-git add <file1> <file2> ...
-
-# Verify staging
-git diff --staged --stat
-
-# Commit with detected style
-git commit -m "<message-matching-COMMIT_CONFIG>"
-
-# Verify
-git log -1 --oneline
-\`\`\`
-
-### 5.4 Commit Message Generation
-
-**Based on COMMIT_CONFIG from Phase 1:**
-
-\`\`\`
-IF style == SEMANTIC AND language == KOREAN:
-  -> "feat: \uB85C\uADF8\uC778 \uAE30\uB2A5 \uCD94\uAC00"
-  
-IF style == SEMANTIC AND language == ENGLISH:
-  -> "feat: add login feature"
-  
-IF style == PLAIN AND language == KOREAN:
-  -> "\uB85C\uADF8\uC778 \uAE30\uB2A5 \uCD94\uAC00"
-  
-IF style == PLAIN AND language == ENGLISH:
-  -> "Add login feature"
-  
-IF style == SHORT:
-  -> "format" / "type fix" / "lint"
-\`\`\`
-
-**VALIDATION before each commit:**
-1. Does message match detected style?
-2. Does language match detected language?
-3. Is it similar to examples from git log?
-
-If ANY check fails -> REWRITE message.
-
-### 5.5 Commit Footer & Co-Author (Configurable)
-
-**Check oh-my-opencode.json for these flags:**
-- \`git_master.commit_footer\` (default: true) - adds footer message
-- \`git_master.include_co_authored_by\` (default: true) - adds co-author trailer
-
-If enabled, add Sisyphus attribution to EVERY commit:
-
-1. **Footer in commit body (if \`commit_footer: true\`):**
-\`\`\`
-Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-opencode)
-\`\`\`
-
-2. **Co-authored-by trailer (if \`include_co_authored_by: true\`):**
-\`\`\`
-Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
-\`\`\`
-
-**Example (both enabled):**
-\`\`\`bash
-git commit -m "{Commit Message}" -m "Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-opencode)" -m "Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>"
-\`\`\`
-
-**To disable:** Set in oh-my-opencode.json:
-\`\`\`json
-{ "git_master": { "commit_footer": false, "include_co_authored_by": false } }
-\`\`\`
-</execution>
-
----
-
-## PHASE 6: Verification & Cleanup
-
-<verification>
-### 6.1 Post-Commit Verification
-
-\`\`\`bash
-# Check working directory clean
-git status
-
-# Review new history
-git log --oneline $(git merge-base HEAD main 2>/dev/null || git merge-base HEAD master)..HEAD
-
-# Verify each commit is atomic
-# (mentally check: can each be reverted independently?)
-\`\`\`
-
-### 6.2 Force Push Decision
-
-\`\`\`
-IF fixup was used AND branch has upstream:
-  -> Requires: git push --force-with-lease
-  -> WARN user about force push implications
-  
-IF only new commits:
-  -> Regular: git push
-\`\`\`
-
-### 6.3 Final Report
+## PHASE 4-6: Execution & Verification
 
-\`\`\`
-COMMIT SUMMARY:
-  Strategy: <what was done>
-  Commits created: N
-  Fixups merged: M
-  
-HISTORY:
-  <hash1> <message1>
-  <hash2> <message2>
-  ...
-
-NEXT STEPS:
-  - git push [--force-with-lease]
-  - Create PR if ready
-\`\`\`
-</verification>
-
----
+Execute commits in dependency order, verify each, then final report.
 
 ## Quick Reference
 
-### Style Detection Cheat Sheet
-
-| If git log shows... | Use this style |
-|---------------------|----------------|
-| \`feat: xxx\`, \`fix: yyy\` | SEMANTIC |
-| \`Add xxx\`, \`Fix yyy\`, \`xxx \uCD94\uAC00\` | PLAIN |
-| \`format\`, \`lint\`, \`typo\` | SHORT |
-| Full sentences | SENTENCE |
-| Mix of above | Use MAJORITY (not semantic by default) |
-
-### Decision Tree
-
-\`\`\`
-Is this on main/master?
-  YES -> NEW_COMMITS_ONLY, never rewrite
-  NO -> Continue
-
-Are all commits local (not pushed)?
-  YES -> AGGRESSIVE_REWRITE allowed
-  NO -> CAREFUL_REWRITE (warn on force push)
-
-Does change complement existing commit?
-  YES -> FIXUP to that commit
-  NO -> NEW COMMIT
-
-Is history messy?
-  YES + all local -> Consider RESET_REBUILD
-  NO -> Normal flow
-\`\`\`
-
-### Anti-Patterns (AUTOMATIC FAILURE)
-
-1. **NEVER make one giant commit** - 3+ files MUST be 2+ commits
-2. **NEVER default to semantic commits** - detect from git log first
-3. **NEVER separate test from implementation** - same commit always
-4. **NEVER group by file type** - group by feature/module
-5. **NEVER rewrite pushed history** without explicit permission
-6. **NEVER leave working directory dirty** - complete all changes
-7. **NEVER skip JUSTIFICATION** - explain why files are grouped
-8. **NEVER use vague grouping reasons** - "related to X" is NOT valid
-
----
-
-## FINAL CHECK BEFORE EXECUTION (BLOCKING)
-
-\`\`\`
-STOP AND VERIFY - Do not proceed until ALL boxes checked:
-
-[] File count check: N files -> at least ceil(N/3) commits?
-  - 3 files -> min 1 commit
-  - 5 files -> min 2 commits
-  - 10 files -> min 4 commits
-  - 20 files -> min 7 commits
-
-[] Justification check: For each commit with 3+ files, did I write WHY?
-
-[] Directory split check: Different directories -> different commits?
-
-[] Test pairing check: Each test with its implementation?
-
-[] Dependency order check: Foundations before dependents?
-\`\`\`
-
-**HARD STOP CONDITIONS:**
-- Making 1 commit from 3+ files -> **WRONG. SPLIT.**
-- Making 2 commits from 10+ files -> **WRONG. SPLIT MORE.**
-- Can't justify file grouping in one sentence -> **WRONG. SPLIT.**
-- Different directories in same commit (without justification) -> **WRONG. SPLIT.**
-
----
----
-
-# REBASE MODE (Phase R1-R4)
-
-## PHASE R1: Rebase Context Analysis
-
-<rebase_context>
-### R1.1 Parallel Information Gathering
-
-\`\`\`bash
-# Execute ALL in parallel
-git branch --show-current
-git log --oneline -20
-git merge-base HEAD main 2>/dev/null || git merge-base HEAD master
-git rev-parse --abbrev-ref @{upstream} 2>/dev/null || echo "NO_UPSTREAM"
-git status --porcelain
-git stash list
-\`\`\`
-
-### R1.2 Safety Assessment
-
-| Condition | Risk Level | Action |
-|-----------|------------|--------|
-| On main/master | CRITICAL | **ABORT** - never rebase main |
-| Dirty working directory | WARNING | Stash first: \`git stash push -m "pre-rebase"\` |
-| Pushed commits exist | WARNING | Will require force-push; confirm with user |
-| All commits local | SAFE | Proceed freely |
-| Upstream diverged | WARNING | May need \`--onto\` strategy |
-
-### R1.3 Determine Rebase Strategy
-
-\`\`\`
-USER REQUEST -> STRATEGY:
-
-"squash commits" / "cleanup" / "\uC815\uB9AC"
-  -> INTERACTIVE_SQUASH
-
-"rebase on main" / "update branch" / "\uBA54\uC778\uC5D0 \uB9AC\uBCA0\uC774\uC2A4"
-  -> REBASE_ONTO_BASE
-
-"autosquash" / "apply fixups"
-  -> AUTOSQUASH
-
-"reorder commits" / "\uCEE4\uBC0B \uC21C\uC11C"
-  -> INTERACTIVE_REORDER
-
-"split commit" / "\uCEE4\uBC0B \uBD84\uB9AC"
-  -> INTERACTIVE_EDIT
-\`\`\`
-</rebase_context>
-
----
-
-## PHASE R2: Rebase Execution
-
-<rebase_execution>
-### R2.1 Interactive Rebase (Squash/Reorder)
-
-\`\`\`bash
-# Find merge-base
-MERGE_BASE=$(git merge-base HEAD main 2>/dev/null || git merge-base HEAD master)
-
-# Start interactive rebase
-# NOTE: Cannot use -i interactively. Use GIT_SEQUENCE_EDITOR for automation.
-
-# For SQUASH (combine all into one):
-git reset --soft $MERGE_BASE
-git commit -m "Combined: <summarize all changes>"
-
-# For SELECTIVE SQUASH (keep some, squash others):
-# Use fixup approach - mark commits to squash, then autosquash
-\`\`\`
-
-### R2.2 Autosquash Workflow
-
-\`\`\`bash
-# When you have fixup! or squash! commits:
-MERGE_BASE=$(git merge-base HEAD main 2>/dev/null || git merge-base HEAD master)
-GIT_SEQUENCE_EDITOR=: git rebase -i --autosquash $MERGE_BASE
-
-# The GIT_SEQUENCE_EDITOR=: trick auto-accepts the rebase todo
-# Fixup commits automatically merge into their targets
-\`\`\`
-
-### R2.3 Rebase Onto (Branch Update)
-
-\`\`\`bash
-# Scenario: Your branch is behind main, need to update
-
-# Simple rebase onto main:
-git fetch origin
-git rebase origin/main
-
-# Complex: Move commits to different base
-# git rebase --onto <newbase> <oldbase> <branch>
-git rebase --onto origin/main $(git merge-base HEAD origin/main) HEAD
-\`\`\`
-
-### R2.4 Handling Conflicts
-
-\`\`\`
-CONFLICT DETECTED -> WORKFLOW:
-
-1. Identify conflicting files:
-   git status | grep "both modified"
-
-2. For each conflict:
-   - Read the file
-   - Understand both versions (HEAD vs incoming)
-   - Resolve by editing file
-   - Remove conflict markers (<<<<, ====, >>>>)
-
-3. Stage resolved files:
-   git add <resolved-file>
-
-4. Continue rebase:
-   git rebase --continue
-
-5. If stuck or confused:
-   git rebase --abort  # Safe rollback
-\`\`\`
-
-### R2.5 Recovery Procedures
-
-| Situation | Command | Notes |
-|-----------|---------|-------|
-| Rebase going wrong | \`git rebase --abort\` | Returns to pre-rebase state |
-| Need original commits | \`git reflog\` -> \`git reset --hard <hash>\` | Reflog keeps 90 days |
-| Accidentally force-pushed | \`git reflog\` -> coordinate with team | May need to notify others |
-| Lost commits after rebase | \`git fsck --lost-found\` | Nuclear option |
-</rebase_execution>
-
----
-
-## PHASE R3: Post-Rebase Verification
-
-<rebase_verify>
-\`\`\`bash
-# Verify clean state
-git status
-
-# Check new history
-git log --oneline $(git merge-base HEAD main 2>/dev/null || git merge-base HEAD master)..HEAD
-
-# Verify code still works (if tests exist)
-# Run project-specific test command
-
-# Compare with pre-rebase if needed
-git diff ORIG_HEAD..HEAD --stat
-\`\`\`
-
-### Push Strategy
-
-\`\`\`
-IF branch never pushed:
-  -> git push -u origin <branch>
-
-IF branch already pushed:
-  -> git push --force-with-lease origin <branch>
-  -> ALWAYS use --force-with-lease (not --force)
-  -> Prevents overwriting others' work
-\`\`\`
-</rebase_verify>
-
----
-
-## PHASE R4: Rebase Report
-
-\`\`\`
-REBASE SUMMARY:
-  Strategy: <SQUASH | AUTOSQUASH | ONTO | REORDER>
-  Commits before: N
-  Commits after: M
-  Conflicts resolved: K
-  
-HISTORY (after rebase):
-  <hash1> <message1>
-  <hash2> <message2>
-
-NEXT STEPS:
-  - git push --force-with-lease origin <branch>
-  - Review changes before merge
-\`\`\`
-
----
----
-
-# HISTORY SEARCH MODE (Phase H1-H3)
-
-## PHASE H1: Determine Search Type
-
-<history_search_type>
-### H1.1 Parse User Request
-
-| User Request | Search Type | Tool |
-|--------------|-------------|------|
-| "when was X added" / "X\uAC00 \uC5B8\uC81C \uCD94\uAC00\uB410\uC5B4" | PICKAXE | \`git log -S\` |
-| "find commits changing X pattern" | REGEX | \`git log -G\` |
-| "who wrote this line" / "\uC774 \uC904 \uB204\uAC00 \uC37C\uC5B4" | BLAME | \`git blame\` |
-| "when did bug start" / "\uBC84\uADF8 \uC5B8\uC81C \uC0DD\uACBC\uC5B4" | BISECT | \`git bisect\` |
-| "history of file" / "\uD30C\uC77C \uD788\uC2A4\uD1A0\uB9AC" | FILE_LOG | \`git log -- path\` |
-| "find deleted code" / "\uC0AD\uC81C\uB41C \uCF54\uB4DC \uCC3E\uAE30" | PICKAXE_ALL | \`git log -S --all\` |
-
-### H1.2 Extract Search Parameters
-
-\`\`\`
-From user request, identify:
-- SEARCH_TERM: The string/pattern to find
-- FILE_SCOPE: Specific file(s) or entire repo
-- TIME_RANGE: All time or specific period
-- BRANCH_SCOPE: Current branch or --all branches
-\`\`\`
-</history_search_type>
-
----
-
-## PHASE H2: Execute Search
-
-<history_search_exec>
-### H2.1 Pickaxe Search (git log -S)
-
-**Purpose**: Find commits that ADD or REMOVE a specific string
-
-\`\`\`bash
-# Basic: Find when string was added/removed
-git log -S "searchString" --oneline
-
-# With context (see the actual changes):
-git log -S "searchString" -p
-
-# In specific file:
-git log -S "searchString" -- path/to/file.py
-
-# Across all branches (find deleted code):
-git log -S "searchString" --all --oneline
-
-# With date range:
-git log -S "searchString" --since="2024-01-01" --oneline
-
-# Case insensitive:
-git log -S "searchstring" -i --oneline
-\`\`\`
-
-**Example Use Cases:**
-\`\`\`bash
-# When was this function added?
-git log -S "def calculate_discount" --oneline
-
-# When was this constant removed?
-git log -S "MAX_RETRY_COUNT" --all --oneline
-
-# Find who introduced a bug pattern
-git log -S "== None" -- "*.py" --oneline  # Should be "is None"
-\`\`\`
-
-### H2.2 Regex Search (git log -G)
-
-**Purpose**: Find commits where diff MATCHES a regex pattern
-
-\`\`\`bash
-# Find commits touching lines matching pattern
-git log -G "pattern.*regex" --oneline
-
-# Find function definition changes
-git log -G "def\\s+my_function" --oneline -p
-
-# Find import changes
-git log -G "^import\\s+requests" -- "*.py" --oneline
-
-# Find TODO additions/removals
-git log -G "TODO|FIXME|HACK" --oneline
-\`\`\`
-
-**-S vs -G Difference:**
-\`\`\`
--S "foo": Finds commits where COUNT of "foo" changed
--G "foo": Finds commits where DIFF contains "foo"
-
-Use -S for: "when was X added/removed"
-Use -G for: "what commits touched lines containing X"
-\`\`\`
-
-### H2.3 Git Blame
-
-**Purpose**: Line-by-line attribution
-
-\`\`\`bash
-# Basic blame
-git blame path/to/file.py
-
-# Specific line range
-git blame -L 10,20 path/to/file.py
-
-# Show original commit (ignoring moves/copies)
-git blame -C path/to/file.py
-
-# Ignore whitespace changes
-git blame -w path/to/file.py
-
-# Show email instead of name
-git blame -e path/to/file.py
-
-# Output format for parsing
-git blame --porcelain path/to/file.py
-\`\`\`
-
-**Reading Blame Output:**
-\`\`\`
-^abc1234 (Author Name 2024-01-15 10:30:00 +0900 42) code_line_here
-|         |            |                       |    +-- Line content
-|         |            |                       +-- Line number
-|         |            +-- Timestamp
-|         +-- Author
-+-- Commit hash (^ means initial commit)
-\`\`\`
-
-### H2.4 Git Bisect (Binary Search for Bugs)
-
-**Purpose**: Find exact commit that introduced a bug
-
-\`\`\`bash
-# Start bisect session
-git bisect start
-
-# Mark current (bad) state
-git bisect bad
-
-# Mark known good commit (e.g., last release)
-git bisect good v1.0.0
-
-# Git checkouts middle commit. Test it, then:
-git bisect good  # if this commit is OK
-git bisect bad   # if this commit has the bug
-
-# Repeat until git finds the culprit commit
-# Git will output: "abc1234 is the first bad commit"
-
-# When done, return to original state
-git bisect reset
-\`\`\`
-
-**Automated Bisect (with test script):**
-\`\`\`bash
-# If you have a test that fails on bug:
-git bisect start
-git bisect bad HEAD
-git bisect good v1.0.0
-git bisect run pytest tests/test_specific.py
-
-# Git runs test on each commit automatically
-# Exits 0 = good, exits 1-127 = bad, exits 125 = skip
-\`\`\`
-
-### H2.5 File History Tracking
-
-\`\`\`bash
-# Full history of a file
-git log --oneline -- path/to/file.py
-
-# Follow file across renames
-git log --follow --oneline -- path/to/file.py
-
-# Show actual changes
-git log -p -- path/to/file.py
-
-# Files that no longer exist
-git log --all --full-history -- "**/deleted_file.py"
-
-# Who changed file most
-git shortlog -sn -- path/to/file.py
-\`\`\`
-</history_search_exec>
-
----
-
-## PHASE H3: Present Results
-
-<history_results>
-### H3.1 Format Search Results
-
-\`\`\`
-SEARCH QUERY: "<what user asked>"
-SEARCH TYPE: <PICKAXE | REGEX | BLAME | BISECT | FILE_LOG>
-COMMAND USED: git log -S "..." ...
-
-RESULTS:
-  Commit       Date           Message
-  ---------    ----------     --------------------------------
-  abc1234      2024-06-15     feat: add discount calculation
-  def5678      2024-05-20     refactor: extract pricing logic
-
-MOST RELEVANT COMMIT: abc1234
-DETAILS:
-  Author: John Doe <john@example.com>
-  Date: 2024-06-15
-  Files changed: 3
-  
-DIFF EXCERPT (if applicable):
-  + def calculate_discount(price, rate):
-  +     return price * (1 - rate)
-\`\`\`
-
-### H3.2 Provide Actionable Context
-
-Based on search results, offer relevant follow-ups:
-
-\`\`\`
-FOUND THAT commit abc1234 introduced the change.
-
-POTENTIAL ACTIONS:
-- View full commit: git show abc1234
-- Revert this commit: git revert abc1234
-- See related commits: git log --ancestry-path abc1234..HEAD
-- Cherry-pick to another branch: git cherry-pick abc1234
-\`\`\`
-</history_results>
-
----
-
-## Quick Reference: History Search Commands
-
 | Goal | Command |
 |------|---------|
 | When was "X" added? | \`git log -S "X" --oneline\` |
-| When was "X" removed? | \`git log -S "X" --all --oneline\` |
-| What commits touched "X"? | \`git log -G "X" --oneline\` |
 | Who wrote line N? | \`git blame -L N,N file.py\` |
 | When did bug start? | \`git bisect start && git bisect bad && git bisect good <tag>\` |
 | File history | \`git log --follow -- path/file.py\` |
-| Find deleted file | \`git log --all --full-history -- "**/filename"\` |
-| Author stats for file | \`git shortlog -sn -- path/file.py\` |
 
----
-
-## Anti-Patterns (ALL MODES)
+## Anti-Patterns
 
-### Commit Mode
 - One commit for many files -> SPLIT
 - Default to semantic style -> DETECT first
-
-### Rebase Mode
 - Rebase main/master -> NEVER
-- \`--force\` instead of \`--force-with-lease\` -> DANGEROUS
-- Rebase without stashing dirty files -> WILL FAIL
-
-### History Search Mode
-- \`-S\` when \`-G\` is appropriate -> Wrong results
-- Blame without \`-C\` on moved code -> Wrong attribution
-- Bisect without proper good/bad boundaries -> Wasted time`
+- \`--force\` instead of \`--force-with-lease\` -> DANGEROUS`
 };
 function createBuiltinSkills() {
+  const maestroSkills = createMaestroSkills();
   return [
-    maestroCoreSkill,
-    designingSkill,
     conductorSkill,
-    orchestratorSkill,
     trackingSkill,
     playwrightSkill,
     frontendUiUxSkill,
-    gitMasterSkill
+    gitMasterSkill,
+    ...maestroSkills
   ];
 }
 
 // src/features/opencode-skill-loader/skill-content.ts
-var MAESTRO_SKILLS = new Set([
-  "designing",
-  "conductor",
-  "orchestrator",
-  "tracking"
-]);
 function resolveMultipleSkills(skillNames) {
   const skills = createBuiltinSkills();
   const skillMap = new Map(skills.map((s) => [s.name, s.template]));
   const resolved = new Map;
   const notFound = [];
-  const hasMaestroSkill = skillNames.some((name) => MAESTRO_SKILLS.has(name));
-  if (hasMaestroSkill && !skillNames.includes("maestro-core")) {
-    const maestroCoreTemplate = skillMap.get("maestro-core");
-    if (maestroCoreTemplate) {
-      resolved.set("maestro-core", maestroCoreTemplate);
-    }
-  }
   for (const name of skillNames) {
     const template = skillMap.get(name);
     if (template) {
@@ -23265,8 +22293,9 @@ Return your findings and recommendations. The actual implementation will be hand
 
 // src/hooks/prometheus-md-only/index.ts
 function isAllowedFile(filePath) {
-  const hasAllowedExtension = ALLOWED_EXTENSIONS.some((ext) => filePath.endsWith(ext));
-  const isInAllowedPath = filePath.includes(ALLOWED_PATH_PREFIX);
+  const normalizedPath = filePath.replace(/\\/g, "/");
+  const hasAllowedExtension = ALLOWED_EXTENSIONS.some((ext) => normalizedPath.endsWith(ext));
+  const isInAllowedPath = normalizedPath.includes(ALLOWED_PATH_PREFIX);
   return hasAllowedExtension && isInAllowedPath;
 }
 function getMessageDir9(sessionID) {
@@ -44701,8 +43730,13 @@ Session ID: ${task.sessionID}
 
 (No assistant response found)`;
   }
-  const lastMessage = assistantMessages[assistantMessages.length - 1];
-  const textParts = lastMessage?.parts?.filter((p2) => p2.type === "text") ?? [];
+  const sortedMessages = [...assistantMessages].sort((a, b3) => {
+    const timeA = String(a.info?.time ?? "");
+    const timeB = String(b3.info?.time ?? "");
+    return timeB.localeCompare(timeA);
+  });
+  const lastMessage = sortedMessages[0];
+  const textParts = lastMessage.parts?.filter((p2) => p2.type === "text") ?? [];
   const textContent = textParts.map((p2) => p2.text ?? "").filter((text) => text.length > 0).join(`
 `);
   const duration3 = formatDuration(task.startedAt, task.completedAt);
@@ -45738,10 +44772,12 @@ class ConcurrencyManager {
 
 // src/features/background-agent/manager.ts
 var TASK_TTL_MS = 30 * 60 * 1000;
+var MIN_STABILITY_TIME_MS = 10 * 1000;
 
 class BackgroundManager {
   tasks;
   notifications;
+  pendingNotifications;
   client;
   directory;
   pollingInterval;
@@ -45749,6 +44785,7 @@ class BackgroundManager {
   constructor(ctx, config3) {
     this.tasks = new Map;
     this.notifications = new Map;
+    this.pendingNotifications = new Map;
     this.client = ctx.client;
     this.directory = ctx.directory;
     this.concurrencyManager = new ConcurrencyManager(config3);
@@ -46029,6 +45066,15 @@ class BackgroundManager {
   clearNotifications(sessionID) {
     this.notifications.delete(sessionID);
   }
+  hasPendingNotifications(sessionID) {
+    const pending = this.pendingNotifications.get(sessionID);
+    return pending !== undefined && pending.length > 0;
+  }
+  consumePendingNotifications(sessionID) {
+    const pending = this.pendingNotifications.get(sessionID) ?? [];
+    this.pendingNotifications.delete(sessionID);
+    return pending;
+  }
   clearNotificationsForTask(taskId) {
     for (const [sessionID, tasks] of this.notifications.entries()) {
       const filtered = tasks.filter((t) => t.id !== taskId);
@@ -46057,6 +45103,7 @@ class BackgroundManager {
     this.stopPolling();
     this.tasks.clear();
     this.notifications.clear();
+    this.pendingNotifications.clear();
   }
   notifyParentSession(task) {
     const duration3 = this.formatDuration(task.startedAt, task.completedAt);
@@ -46069,37 +45116,30 @@ class BackgroundManager {
         duration: duration3
       });
     }
-    const message = `[BACKGROUND TASK COMPLETED] Task "${task.description}" finished in ${duration3}. Use background_output with task_id="${task.id}" to get results.`;
-    log("[background-agent] Sending notification to parent session:", { parentSessionID: task.parentSessionID });
+    const notification = {
+      taskId: task.id,
+      description: task.description,
+      duration: duration3,
+      status: task.status === "error" ? "error" : "completed",
+      error: task.error
+    };
+    const existing = this.pendingNotifications.get(task.parentSessionID) ?? [];
+    existing.push(notification);
+    this.pendingNotifications.set(task.parentSessionID, existing);
+    log("[background-agent] Stored pending notification for parent session:", {
+      parentSessionID: task.parentSessionID,
+      taskId: task.id
+    });
     const taskId = task.id;
-    setTimeout(async () => {
+    setTimeout(() => {
       if (task.concurrencyKey) {
         this.concurrencyManager.release(task.concurrencyKey);
+        task.concurrencyKey = undefined;
       }
-      try {
-        const body = {
-          parts: [{ type: "text", text: message }]
-        };
-        if (task.parentAgent !== undefined) {
-          body.agent = task.parentAgent;
-        }
-        if (task.parentModel?.providerID && task.parentModel?.modelID) {
-          body.model = { providerID: task.parentModel.providerID, modelID: task.parentModel.modelID };
-        }
-        await this.client.session.prompt({
-          path: { id: task.parentSessionID },
-          body,
-          query: { directory: this.directory }
-        });
-        log("[background-agent] Successfully sent prompt to parent session:", { parentSessionID: task.parentSessionID });
-      } catch (error45) {
-        log("[background-agent] prompt failed:", String(error45));
-      } finally {
-        this.clearNotificationsForTask(taskId);
-        this.tasks.delete(taskId);
-        log("[background-agent] Removed completed task from memory:", taskId);
-      }
-    }, 200);
+      this.clearNotificationsForTask(taskId);
+      this.tasks.delete(taskId);
+      log("[background-agent] Removed completed task from memory:", taskId);
+    }, 5 * 60 * 1000);
   }
   formatDuration(start, end) {
     const duration3 = (end ?? new Date).getTime() - start.getTime();
@@ -46162,11 +45202,7 @@ class BackgroundManager {
         continue;
       try {
         const sessionStatus = allStatuses[task.sessionID];
-        if (!sessionStatus) {
-          log("[background-agent] Session not found in status:", task.sessionID);
-          continue;
-        }
-        if (sessionStatus.type === "idle") {
+        if (sessionStatus?.type === "idle") {
           const hasIncompleteTodos2 = await this.checkSessionTodos(task.sessionID);
           if (hasIncompleteTodos2) {
             log("[background-agent] Task has incomplete todos via polling, waiting:", task.id);
@@ -46210,6 +45246,27 @@ class BackgroundManager {
             task.progress.lastMessage = lastMessage;
             task.progress.lastMessageAt = new Date;
           }
+          const currentMsgCount = messages.length;
+          const elapsedMs = Date.now() - task.startedAt.getTime();
+          if (elapsedMs >= MIN_STABILITY_TIME_MS) {
+            if (task.lastMsgCount === currentMsgCount) {
+              task.stablePolls = (task.stablePolls ?? 0) + 1;
+              if (task.stablePolls >= 3) {
+                const hasIncompleteTodos2 = await this.checkSessionTodos(task.sessionID);
+                if (!hasIncompleteTodos2) {
+                  task.status = "completed";
+                  task.completedAt = new Date;
+                  this.markForNotification(task);
+                  this.notifyParentSession(task);
+                  log("[background-agent] Task completed via stability detection:", task.id);
+                  continue;
+                }
+              }
+            } else {
+              task.stablePolls = 0;
+            }
+          }
+          task.lastMsgCount = currentMsgCount;
         }
       } catch (error45) {
         log("[background-agent] Poll error for task:", { taskId: task.id, error: error45 });
@@ -56588,6 +55645,7 @@ var OhMyOpenCodePlugin = async (ctx) => {
       await editErrorRecovery?.["tool.execute.after"](input, output);
       await sisyphusOrchestrator?.["tool.execute.after"]?.(input, output);
       await taskResumeInfo["tool.execute.after"](input, output);
+      await backgroundNotificationHook?.["tool.execute.after"]?.(input, output);
     }
   };
 };