opencodekit 0.17.8 → 0.17.10

package/dist/template/.opencode/skill/swarm-coordination/SKILL.md

@@ -15,10 +15,11 @@ Coordinate multiple agents working on independent tasks in parallel using Kimi K
 
 ## Overview
 
-**Swarm = Leader + Workers + Progress Tracking + Todo Persistence**
+**Swarm = Leader + Workers + Reconciler + Progress Tracking + Todo Persistence**
 
 - **Leader (build agent)**: Orchestrates the swarm - analyzes tasks, spawns workers, monitors progress, synthesizes results
 - **Workers (general/explore/review/plan agents)**: Execute independent tasks - read delegation, make changes, report progress
+- **Reconciler**: Watches for CI failures, detects broken builds, auto-spawns fix tasks - this is the self-healing mechanism
 - **Progress Tracker (swarm-progress.jsonl)**: Real-time progress updates with TUI visualization
 - **Todo Persistence (swarm-todos.json)**: Cross-session recovery for interrupted swarms
 
@@ -68,8 +69,8 @@ Coordinate multiple agents working on independent tasks in parallel using Kimi K
 │  - Monitors progress via swarm tool                             │
 │  - Synthesizes final results                                     │
 └─────────────────────────────────────────────────────────────────┘
-         │                    │                    │
-         ▼                    ▼                    ▼
+          │                    │                    │
+          ▼                    ▼                    ▼
 ┌─────────────┐      ┌─────────────┐      ┌─────────────┐
 │  WORKER-1   │      │  WORKER-2   │      │  WORKER-3   │
 │  (general)  │      │  (general)  │      │  (general)  │
@@ -79,15 +80,288 @@ Coordinate multiple agents working on independent tasks in parallel using Kimi K
 │ - Execute   │      │ - Execute   │      │ - Execute   │
 │ - Report    │      │ - Report    │      │ - Report    │
 └─────────────┘      └─────────────┘      └─────────────┘
-         │                    │                    │
-         └────────────────────┼────────────────────┘
-                              ▼
-                    ┌─────────────────┐
-                    │  PROGRESS +     │
-                    │  TODO PERSIST   │
-                    └─────────────────┘
+          │                    │                    │
+          └────────────────────┼────────────────────┘
+                               ▼
+                     ┌─────────────────┐
+                     │   RECONCILER    │
+                     │                 │
+                     │ - Watch CI      │
+                     │ - Detect broken │
+                     │ - Spawn fixes   │
+                     └─────────────────┘
+                               │
+                               ▼
+                     ┌─────────────────┐
+                     │  PROGRESS +     │
+                     │  TODO PERSIST   │
+                     └─────────────────┘
 ```
 
+## Reconciler Agent Pattern (Self-Healing)
+
+The reconciler is the key to scaling beyond 50+ agents. Without reconciliation, broken builds cascade and the swarm collapses. The reconciler provides **continuous self-healing** by watching for failures and spawning targeted fix tasks.
+
+### When to Use Reconciler
+
+- **50+ agents** running in parallel → **REQUIRED**
+- **10-50 agents** → Recommended
+- **<10 agents** → Optional (leader can handle)
+
+### Reconciler Responsibilities
+
+1. **Watch CI/Build Status**: Monitor build gates continuously
+2. **Detect Failures**: Identify which worker caused the failure
+3. **Analyze Root Cause**: Determine if it's a merge conflict, test failure, or type error
+4. **Spawn Fix Tasks**: Create targeted fix tasks with context about what failed
+5. **Verify Fix**: Wait for fix to pass gates before continuing
+
+### Reconciler vs Leader
+
+| Aspect         | Leader                        | Reconciler                    |
+| -------------- | ----------------------------- | ----------------------------- |
+| Focus          | Orchestration, spawning       | Recovery, fixing              |
+| Runs           | At swarm start, between waves | Continuously during execution |
+| On failure     | Spawns workers                | Spawns fix tasks              |
+| Failure impact | Can't start work              | Wave can't complete           |
+
+### Implementing Reconciler
+
+The reconciler runs in a loop during swarm execution:
+
+```typescript
+// Reconciler runs in background during swarm execution
+async function runReconciler(teamName: string, buildCommand: string) {
+  while (swarmActive) {
+    // 1. Check build status
+    const status = await swarm({
+      operation: "monitor",
+      operation: "status",
+      team_name: teamName,
+    });
+    const stats = JSON.parse(status).summary;
+
+    // 2. If there are errors, investigate
+    if (stats.errors > 0) {
+      // 3. Get error details
+      const errors = await getWorkerErrors(teamName);
+
+      for (const error of errors) {
+        // 4. Analyze root cause
+        const cause = await analyzeError(error);
+
+        // 5. Spawn fix task
+        const fixBead = await br create({
+          title: `Fix: ${cause.summary}`,
+          type: "bug",
+          description: `Detected by reconciler: ${error.message}. Root cause: ${cause.rootCause}. Suggested fix: ${cause.suggestion}`,
+        });
+
+        // 6. Assign to targeted worker
+        await Task({
+          subagent_type: "general",
+          description: `Fix ${error.worker}`,
+          prompt: `Fix the error in ${error.file}.
+
+Error: ${error.message}
+Root cause: ${cause.rootCause}
+Suggested fix: ${cause.suggestion}
+
+Run: ${buildCommand}
+Verify: npm run typecheck && npm run lint`,
+        });
+      }
+    }
+
+    // Wait before next check
+    await sleep(30000); // Check every 30 seconds
+  }
+}
+```
+
+### Error Analysis Patterns
+
+The reconciler categorizes errors:
+
+| Error Type     | Detection                        | Fix Strategy                 |
+| -------------- | -------------------------------- | ---------------------------- |
+| Merge conflict | "CONFLICT" in output, git status | Re-base, resolve, force push |
+| Type error     | "typecheck failed"               | Fix types, run typecheck     |
+| Test failure   | "test failed", "expect" mismatch | Fix test or implementation   |
+| Lint error     | "lint failed", formatting issues | Run lint:fix                 |
+| Build error    | "build failed", bundler errors   | Fix imports, dependencies    |
+
+### Spawning Fix Tasks
+
+When the reconciler spawns a fix task, it includes:
+
+```typescript
+// Create fix task with full context
+await br create({
+  title: `Fix: ${error.type} in ${error.file}`,
+  type: "bug",
+  description: `## Error Detected
+- Worker: ${error.worker}
+- File: ${error.file}
+- Error: ${error.message}
+- Timestamp: ${error.timestamp}
+
+## Root Cause Analysis
+${cause.explanation}
+
+## Suggested Fix
+${cause.suggestion}
+
+## Verification
+Run: ${buildCommand}
+Must pass before wave can complete.`,
+});
+```
+
+### Reconciler in Wave Execution
+
+Add reconciler monitoring to each wave:
+
+```typescript
+// Execute wave with reconciler
+async function executeWaveWithReconciler(wave, teamName) {
+  // Start reconciler in background
+  const reconciler = runReconciler(teamName, "npm run typecheck && npm run lint");
+
+  // Execute workers in this wave
+  await Promise.all(wave.tasks.map(spawnWorker));
+
+  // Wait for all workers + reconciler to complete
+  await reconciler;
+
+  // Verify wave output before proceeding
+  await bash("npm run typecheck && npm run lint");
+}
+```
+
+### Example: Full Swarm with Reconciler
+
+```typescript
+// Full swarm execution with reconciler
+async function runSwarmWithReconciler(tasks, teamName) {
+  // 1. Analyze and create waves
+  const waves = createWaves(tasks);
+
+  // 2. Execute each wave with reconciler
+  for (const wave of waves) {
+    console.log(`Executing wave ${wave.number} with ${wave.tasks.length} tasks`);
+
+    // Start reconciler for this wave
+    const reconcilerPromise = runReconciler(teamName, "npm run typecheck && npm run lint");
+
+    // Spawn workers
+    await Promise.all(wave.tasks.map((task) => spawnWorker(task, teamName)));
+
+    // Wait for reconciler to finish fixing any errors
+    await reconcilerPromise;
+
+    // Verify wave output
+    const result = await bash("npm run typecheck && npm run lint");
+    if (!result.success) {
+      throw new Error(`Wave ${wave.number} failed gates`);
+    }
+
+    console.log(`Wave ${wave.number} complete`);
+  }
+}
+```
+
+## Drift Check After Each Wave
+
+After every wave completes and before starting the next, run a **drift check** to verify the codebase has not deviated from the intended state. Accumulated drift between waves is the primary cause of cascading failures in large swarms.
+
+**Drift** = any difference between actual codebase state and the plan's expected state at a wave boundary.
+
+### What to Check
+
+| Check             | Command                                            | Passing Condition              |
+| ----------------- | -------------------------------------------------- | ------------------------------ |
+| Build gates       | `npm run typecheck && npm run lint`                | Zero errors                    |
+| Unexpected files  | `git diff --name-only HEAD`                        | Only planned files modified    |
+| Missing artifacts | Verify expected files exist                        | All declared outputs present   |
+| Scope adherence   | Compare `git status` vs wave's declared file scope | No out-of-scope files modified |
+
+### Drift Check Protocol
+
+Run after every wave, before spawning the next:
+
+```typescript
+async function driftCheckAfterWave(wave: Wave, expectedFiles: string[]) {
+  console.log(`\n=== DRIFT CHECK: Wave ${wave.number} ===`);
+
+  // 1. Build gates must pass
+  const gates = await bash("npm run typecheck && npm run lint");
+  if (!gates.success) {
+    throw new Error(`Wave ${wave.number} drift: build gates failed\n${gates.output}`);
+  }
+
+  // 2. Detect unexpected file modifications
+  const changedFiles = await bash("git diff --name-only HEAD");
+  const actualFiles = changedFiles.output.trim().split("\n").filter(Boolean);
+  const unexpected = actualFiles.filter((f) => !expectedFiles.includes(f));
+
+  if (unexpected.length > 0) {
+    console.warn(`⚠️  Unexpected files modified in wave ${wave.number}:`);
+    unexpected.forEach((f) => console.warn(`  - ${f}`));
+  }
+
+  // 3. Verify declared artifacts exist
+  for (const artifact of wave.expectedArtifacts ?? []) {
+    const exists = await bash(`test -f ${artifact} && echo "ok" || echo "missing"`);
+    if (exists.output.trim() === "missing") {
+      throw new Error(`Wave ${wave.number} drift: expected artifact missing: ${artifact}`);
+    }
+  }
+
+  console.log(`✓ Drift check passed: Wave ${wave.number}`);
+}
+```
+
+### Integration in Wave Execution
+
+Call drift check between every wave:
+
+```typescript
+for (let i = 0; i < waves.length; i++) {
+  const wave = waves[i];
+  const reconciler = runReconciler(teamName, "npm run typecheck && npm run lint");
+
+  await Promise.all(wave.tasks.map((task) => spawnWorker(task, teamName)));
+  await reconciler;
+
+  // MANDATORY: Drift check before next wave
+  await driftCheckAfterWave(
+    wave,
+    wave.tasks.flatMap((t) => t.assignedFiles),
+  );
+
+  console.log(`✓ Wave ${i + 1}/${waves.length} complete and verified`);
+}
+```
+
+### Drift Response Protocol
+
+| Drift Type               | Severity | Action                                           |
+| ------------------------ | -------- | ------------------------------------------------ |
+| Build gate failure       | Critical | Stop swarm, run reconciler, fix before next wave |
+| Unexpected file modified | Warning  | Review change, revert if out of scope            |
+| Missing artifact         | Critical | Re-run failed worker task, verify output         |
+| Scope creep              | Warning  | Escalate to user if >3 unexpected files changed  |
+
+### When Drift Is Unrecoverable
+
+If drift check fails twice in a row on the same wave:
+
+1. **Stop the swarm** - don't start next wave
+2. **Report to user**: exact drift details, failing gate output, list of unexpected files
+3. **Rollback option**: use `git reset --hard <wave-N-start-tag>` (see `executing-plans` skill)
+4. **Never paper over drift** - proceeding with known drift compounds into cascading failure
+
 ## Swarm Launch Flow - PARL Pattern (7 Steps)
 
 ### Step 0: Task Analysis (Anti-Serial-Collapse + Dependency Graph)
@@ -706,3 +980,84 @@ This renders the beautiful TUI block and shows:
 7. **Use dependency graph** - Spawn workers in parallelizable_groups order
 8. **Graceful shutdown** - Leader waits for all workers, syncs back to Beads
 9. **Use tmux for visibility** - Enable visual monitoring when available
+10. **Use reconciler at scale** - Required for 50+ agents, recommended for 10+
+11. **Reconciler watches continuously** - Spawns fix tasks on detected failures
+
+## Tier Enforcement (Longshot Pattern)
+
+For multi-agent execution at scale (10+ agents), enforce explicit tier hierarchy. This is the Longshot pattern that enabled 200 agents to build Minecraft.
+
+### Tier System
+
+| Tier            | Role                  | Swarm Equivalent | Responsibility                                                 |
+| --------------- | --------------------- | ---------------- | -------------------------------------------------------------- |
+| **planner**     | Lead orchestrator     | Build agent      | Analyzes scope, decomposes into sub-tasks, coordinates workers |
+| **sub-planner** | Mid-level coordinator | N/A              | Takes planner output, further decomposes, assigns to workers   |
+| **worker**      | Execution agent       | Worker agents    | Executes assigned work, reports progress                       |
+
+### When Tiers Are Required
+
+- **<10 agents**: Optional - flat decomposition works
+- **10-50 agents**: Recommended - planner + workers
+- **50+ agents**: Required - planner + sub-planners + workers
+
+### Enforcing Tier Boundaries
+
+The swarm leader enforces tier boundaries:
+
+```typescript
+// Tier enforcement in swarm execution
+async function enforceTiers(waves, tierConfig) {
+  // Wave 1: Planner tasks only
+  const planners = waves.filter((w) => w.tier === "planner");
+  await executeWave(planners);
+
+  // Wave 2: Sub-planner tasks (if any)
+  const subPlanners = waves.filter((w) => w.tier === "sub-planner");
+  await executeWave(subPlanners);
+
+  // Wave 3+: Worker tasks
+  const workers = waves.filter((w) => w.tier === "worker");
+  await executeWave(workers);
+}
+```
+
+### Handoff Contracts Between Tiers
+
+Each tier must declare handoff contracts:
+
+```typescript
+// Planner declares what it produces for sub-planners
+const plannerHandoff = {
+  produces: [
+    { artifact: "docs/auth-design.md", format: "markdown" },
+    { artifact: "tasks/auth-tasks.json", format: "json" },
+  ],
+  consumedBy: ["sub-planner-auth"],
+};
+
+// Worker declares what it consumes from sub-planners
+const workerHandoff = {
+  consumes: [{ artifact: "tasks/auth-tasks.json", format: "json" }],
+  produces: [{ artifact: "src/auth/service.ts", format: "typescript" }],
+};
+```
+
+### Anti-Pattern: Flat Decomposition at Scale
+
+Without tiers, 20 agents get 20 flat tasks → chaos:
+
+- Workers step on each other
+- No coordination between related work
+- Merge conflicts everywhere
+- No clear ownership
+
+With tiers (Longshot pattern):
+
+```
+Lead Planner → Sub-planner A → Worker 1, 2, 3
+              → Sub-planner B → Worker 4, 5, 6
+              Sub-planner C → Worker 7, 8, 9
+```
+
+This mirrors real engineering orgs: lead → tech lead → IC. The architecture is the differentiator.

package/dist/template/.opencode/skill/writing-plans/SKILL.md

@@ -90,10 +90,119 @@ Task C (User API): needs Task A, creates src/api/users.ts
 Wave 1: A, B (parallel)
 Wave 2: C (after Wave 1)
 
+````
+
+## Tiered Task Hierarchy
+
+For multi-agent execution at scale (10+ agents), use explicit tier declarations. This prevents flat decomposition that fails when many agents work in parallel.
+
+### Tier Definitions
+
+| Tier | Role | Description | Example |
+|------|------|-------------|---------|
+| **planner** | Lead orchestrator | Analyzes scope, decomposes into sub-tasks, coordinates workers | "Design auth system" |
+| **sub-planner** | Mid-level coordinator | Takes planner output, further decomposes, assigns to workers | "Break auth into API, model, middleware" |
+| **worker** | Execution agent | Executes assigned work, reports progress | "Implement auth service" |
+
+### When to Use Tiers
+
+- **<10 agents**: Optional - flat decomposition works
+- **10-50 agents**: Recommended - planner + workers
+- **50+ agents**: Required - planner + sub-planners + workers
+
+### Tier Declaration Format
+
+Add tier metadata to each task:
+
+```markdown
+### Task 1: Design Auth System
+
+**Tier:** planner
+
+**Files:**
+- Create: `docs/auth-design.md`
+
+This task decomposes the auth feature into sub-tasks for implementation.
+````
+
+### Handoff Contracts
+
+Tasks must declare what they produce for downstream tasks:
+
+```markdown
+### Handoff Contract
+
+**Produces:**
+
+- `docs/auth-design.md` - Architecture decision document
+
+**Consumed By:**
+
+- Task 2: Implement Auth Service
+- Task 3: Add Auth Tests
+```
+
+### Tier Enforcement in Plans
+
+```markdown
+# [Feature Name] Implementation Plan
+
+> **Tier Structure:**
+>
+> - **Planners (2):** Task 1, Task 5
+> - **Workers (6):** Tasks 2,3,4,6,7,8
+
+## Task Hierarchy
+
+### Tier 1: Planner Tasks (Orchestration)
+
+### Task 1: [Planner] Design Auth System
+
+### Task 5: [Planner] Design API Layer
+
+### Tier 2: Worker Tasks (Execution)
+
+### Task 2: [Worker] Implement Auth Service
+
+### Task 3: [Worker] Add Auth Middleware
+
+### Task 4: [Worker] Write Auth Tests
 ```
 
+### Wave Execution with Tiers
+
+When executing with tiers:
+
+1. **Planner waves** execute first (scope definition)
+2. **Worker waves** execute after planner output is ready
+3. **Sub-planners** sit between, bridging planner → worker
+
+```markdown
+Wave 1 (Planners): Task 1, Task 5
+Wave 2 (Workers): Tasks 2, 3, 4 (after Task 1)
+Wave 3 (Workers): Tasks 6, 7, 8 (after Task 5)
 ```
 
+### Anti-Pattern: Flat Decomposition at Scale
+
+Without tiers, 20 agents get 20 flat tasks → chaos:
+
+- Workers step on each other
+- No coordination between related work
+- Merge conflicts everywhere
+
+With tiers, the structure emerges:
+
+```
+Planner → Sub-planner A → Worker 1, 2, 3
+                     → Worker 4, 5
+        Sub-planner B → Worker 6, 7
+```
+
+This mirrors real engineering orgs: lead → tech lead → IC.
+
+`````
+
 ## Context Budget
 
 Target: ~50% context per plan execution
@@ -130,7 +239,8 @@ Maximum: 2-3 tasks per plan
 def test_specific_behavior():
     result = function(input)
     assert result == expected
-```
+`````
+
 ````
 
 **Step 2: Run test to verify it fails**
@@ -187,3 +297,4 @@ After saving the plan, offer execution choice:
 - Guide them to open new session in worktree
 - **REQUIRED SUB-SKILL:** New session uses skill({ name: "executing-plans" })
 ```
+````

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "opencodekit",
-	"version": "0.17.8",
+	"version": "0.17.10",
 	"description": "CLI tool for bootstrapping and managing OpenCodeKit projects",
 	"keywords": ["agents", "cli", "mcp", "opencode", "opencodekit", "template"],
 	"license": "MIT",
@@ -35,16 +35,16 @@
 		"format:check": "oxfmt --check"
 	},
 	"dependencies": {
-		"@ai-sdk/provider": "^3.0.6",
-		"@ai-sdk/provider-utils": "^4.0.11",
+		"@ai-sdk/provider": "^3.0.8",
+		"@ai-sdk/provider-utils": "^4.0.15",
 		"@clack/prompts": "^0.7.0",
-		"@opencode-ai/plugin": "^1.1.12",
-		"@opentui/core": "^0.1.72",
-		"@opentui/solid": "^0.1.72",
+		"@opencode-ai/plugin": "^1.2.6",
+		"@opentui/core": "^0.1.80",
+		"@opentui/solid": "^0.1.80",
 		"cac": "^6.7.14",
 		"cli-table3": "^0.6.5",
 		"diff": "^8.0.3",
-		"ora": "^9.0.0",
+		"ora": "^9.3.0",
 		"picocolors": "^1.1.1",
 		"solid-js": "1.9.9",
 		"zod": "^3.25.76"
@@ -53,9 +53,9 @@
 		"@biomejs/biome": "^1.9.4",
 		"@types/bun": "latest",
 		"@types/diff": "^8.0.0",
-		"@types/node": "^22.19.5",
+		"@types/node": "^22.19.11",
 		"oxfmt": "^0.23.0",
-		"oxlint": "^1.38.0",
+		"oxlint": "^1.48.0",
 		"typescript": "^5.9.3"
 	},
 	"engines": {