opencode-swarm-plugin 0.35.0 → 0.36.1

package/CHANGELOG.md

@@ -1,5 +1,138 @@
 # opencode-swarm-plugin
 
+## 0.36.1
+
+### Patch Changes
+
+- [`9c1f3f3`](https://github.com/joelhooks/swarm-tools/commit/9c1f3f3e7204f02c133c4a036fa34e83d8376a8c) Thanks [@joelhooks](https://github.com/joelhooks)! - ## 🐝 Coordinator Discipline: Prohibition-First Enforcement
+
+  Coordinators kept "just doing it themselves" after compaction. Now they can't.
+
+  **The Problem:**
+  After context compaction, coordinators would ignore their own instructions to "spawn workers for remaining subtasks" and edit files directly. The compaction context was narrative ("do this") rather than prescriptive ("NEVER do that").
+
+  **The Fix:**
+
+  ### 1. Prohibition-First Compaction Context
+
+  The `SWARM_COMPACTION_CONTEXT` now leads with explicit anti-patterns:
+
+  ```markdown
+  ### ⛔ NEVER DO THESE (Coordinator Anti-Patterns)
+
+  - ❌ **NEVER** use `edit` or `write` tools - SPAWN A WORKER
+  - ❌ **NEVER** run tests with `bash` - SPAWN A WORKER
+  - ❌ **NEVER** implement features yourself - SPAWN A WORKER
+  - ❌ **NEVER** "just do it myself to save time" - NO. SPAWN A WORKER.
+  ```
+
+  ### 2. Runtime Violation Detection
+
+  `detectCoordinatorViolation()` is now wired up in `tool.execute.before`:
+
+  - Detects when coordinators call `edit`, `write`, or test commands
+  - Emits warnings to help coordinators self-correct
+  - Captures VIOLATION events for post-hoc analysis
+
+  ### 3. Coordinator Context Tracking
+
+  New functions track when we're in coordinator mode:
+
+  - `setCoordinatorContext()` - Activated when `hive_create_epic` or `swarm_decompose` is called
+  - `isInCoordinatorContext()` - Checks if we're currently coordinating
+  - `clearCoordinatorContext()` - Cleared when epic is closed
+
+  **Why This Matters:**
+
+  Coordinators that do implementation work burn context, create conflicts, and defeat the purpose of swarm coordination. This fix makes the anti-pattern visible and provides guardrails to prevent it.
+
+  **Validation:**
+
+  - Check `~/.config/swarm-tools/sessions/` for VIOLATION events
+  - Run `coordinator-behavior.eval.ts` to score coordinator discipline
+
+- [`4c23c7a`](https://github.com/joelhooks/swarm-tools/commit/4c23c7a31013bc6537d83a9294b51540056cde93) Thanks [@joelhooks](https://github.com/joelhooks)! - ## Fix Double Hook Registration
+
+  The compaction hook was firing twice per compaction event because OpenCode's plugin loader
+  calls ALL exports as plugin functions. We were exporting `SwarmPlugin` as both:
+
+  1. Named export: `export const SwarmPlugin`
+  2. Default export: `export default SwarmPlugin`
+
+  This caused the plugin to register twice, doubling all hook invocations.
+
+  **Fix:** Changed to default-only export pattern:
+
+  - `src/index.ts`: `const SwarmPlugin` (no export keyword)
+  - `src/plugin.ts`: `export default SwarmPlugin` (no named re-export)
+
+  **Impact:** Compaction hooks now fire once. LLM calls during compaction reduced by 50%.
+
+- Updated dependencies [[`e0c422d`](https://github.com/joelhooks/swarm-tools/commit/e0c422de3f5e15c117cc0cc655c0b03242245be4), [`43c8c93`](https://github.com/joelhooks/swarm-tools/commit/43c8c93ef90b2f04ce59317192334f69d7c4204e)]:
+  - swarm-mail@1.5.1
+
+## 0.36.0
+
+### Minor Changes
+
+- [`ae213aa`](https://github.com/joelhooks/swarm-tools/commit/ae213aa49be977e425e0a767b5b2db16e462f76b) Thanks [@joelhooks](https://github.com/joelhooks)! - ## 🔬 Compaction Hook: Now With X-Ray Vision
+
+  The compaction hook was logging to `console.log` like a caveman. Now it writes structured JSON logs to `~/.config/swarm-tools/logs/compaction.log` - visible via `swarm log compaction`.
+
+  **The Problem:**
+
+  - Plugin wrapper used `console.log` → stdout → invisible
+  - npm package had pino logging → but wrapper didn't use it
+  - Running `/compact` gave zero visibility into what happened
+
+  **The Fix:**
+  Added comprehensive file-based logging throughout the compaction flow:
+
+  ```
+  ┌─────────────────────────────────────────────────────────────┐
+  │                    COMPACTION LOGGING                       │
+  ├─────────────────────────────────────────────────────────────┤
+  │  compaction_hook_invoked     │ Full input/output objects    │
+  │  detect_swarm_*              │ CLI calls, cells, confidence │
+  │  query_swarm_state_*         │ Epic/subtask extraction      │
+  │  generate_compaction_prompt_*│ LLM timing, success/failure  │
+  │  context_injected_via_*      │ Which API used               │
+  │  compaction_complete_*       │ Final result + timing        │
+  └─────────────────────────────────────────────────────────────┘
+  ```
+
+  **Also Enhanced:**
+
+  - SDK message scanning for precise swarm state extraction
+  - Merged scanned state (ground truth) with hive detection (heuristic)
+  - 9 new tests for `scanSessionMessages()` (32 total passing)
+
+  **To See It Work:**
+
+  ```bash
+  swarm setup --reinstall  # Regenerate plugin wrapper
+  # Run /compact in OpenCode
+  swarm log compaction     # See what happened
+  ```
+
+### Patch Changes
+
+- [`5cfc42e`](https://github.com/joelhooks/swarm-tools/commit/5cfc42e93d3e5424e308857a40af4fd9fbda0ba3) Thanks [@joelhooks](https://github.com/joelhooks)! - ## 🐝 Swarm Workers Unchained
+
+  Removed the vestigial `max_subtasks` parameter from decomposition tools. It was dead code - the prompts already say "as many as needed" and the replacement was doing nothing.
+
+  **What changed:**
+
+  - Removed `max_subtasks` arg from `swarm_decompose`, `swarm_plan_prompt`, `swarm_delegate_planning`
+  - Removed from `DecomposeArgsSchema`
+  - Renamed `max_subtasks` → `subtask_count` in eval capture (records actual count, not a limit)
+  - Cleaned up tests that were passing the unused parameter
+
+  **Why it matters:**
+  The LLM decides how many subtasks based on task complexity, not an arbitrary cap. "Plan aggressively" means spawn as many workers as the task needs.
+
+  **No functional change** - the parameter wasn't being used anyway.
+
 ## 0.35.0
 
 ### Minor Changes