opencode-swarm 7.0.1 → 7.0.3

package/dist/tools/__tests__/repo-graph-walk.test.d.ts

@@ -0,0 +1,16 @@
+/**
+ * Regression coverage for the repo-graph walker (issue #704).
+ *
+ * Each test installs a fresh fixture under a tmp dir and asserts the walker
+ * cannot be tricked into:
+ *   - infinite recursion via symlink cycles,
+ *   - exceeding the wall-clock budget on a slow filesystem,
+ *   - exceeding the file cap during traversal (vs. post-truncation),
+ *   - scanning a refused top-level workspace root.
+ *
+ * Symlink-loop coverage is POSIX-only; the test bails on Windows because
+ * creating a directory symlink there requires Developer Mode. The walker's
+ * cycle defense itself is platform-agnostic — see `seenRealPaths` in
+ * src/tools/repo-graph.ts.
+ */
+export {};

package/dist/tools/convene-general-council.d.ts

@@ -1,10 +1,11 @@
 /**
  * General Council Mode — architect-only synthesis tool.
  *
- * The architect spawns council_member subagents in parallel for Round 1,
- * collects their JSON responses, and calls this tool to synthesize results.
- * If the tool detects disagreements and Round 2 deliberation is configured,
- * the architect re-delegates to disputing members and calls this tool again
+ * The architect spawns council_generalist / council_skeptic /
+ * council_domain_expert subagents in parallel for Round 1, collects their
+ * JSON responses, and calls this tool to synthesize results. If the tool
+ * detects disagreements and Round 2 deliberation is configured, the
+ * architect re-delegates to disputing members and calls this tool again
  * with both round1Responses and round2Responses populated.
  *
  * Mirrors the convene-council.ts skeleton but explicitly does NOT inherit

package/dist/tools/repo-graph.d.ts

@@ -206,10 +206,24 @@ export declare function saveIfDirty(workspace: string): Promise<void>;
  * @returns Complete RepoGraph with nodes and edges
  * @throws Error if workspace validation fails
  */
-export declare function buildWorkspaceGraph(workspaceRoot: string, options?: {
+export interface BuildWorkspaceGraphOptions {
     maxFileSizeBytes?: number;
     maxFiles?: number;
-}): RepoGraph;
+    walkBudgetMs?: number;
+    followSymlinks?: boolean;
+}
+export declare function buildWorkspaceGraph(workspaceRoot: string, options?: BuildWorkspaceGraphOptions): RepoGraph;
+/**
+ * Async, event-loop-safe variant of `buildWorkspaceGraph`. The traversal
+ * yields between batches and uses async fs primitives, so callers can run
+ * this from plugin init without freezing the host while a large workspace
+ * is scanned. The per-file processing remains sync — it is CPU-bound symbol
+ * extraction, and the existing per-file caps already prevent runaway work.
+ *
+ * Returned shape matches `buildWorkspaceGraph`. Same homedir guard, same
+ * bounded walk behavior, same deterministic file order.
+ */
+export declare function buildWorkspaceGraphAsync(workspaceRoot: string, options?: BuildWorkspaceGraphOptions): Promise<RepoGraph>;
 /**
  * Incrementally update the graph for a set of changed files.
  * Re-scans only the specified files, updates their nodes and edges,

package/dist/tools/web-search.d.ts

@@ -1,5 +1,5 @@
 /**
- * web_search tool — restricted to council_member agents.
+ * web_search tool — owned by the architect for MODE: COUNCIL pre-search.
  *
  * Thin wrapper around `src/council/web-search-provider.ts`. Returns structured
  * results on success and structured errors on failure (never throws). Config-

package/dist/utils/__tests__/bun-compat.test.d.ts

@@ -0,0 +1,11 @@
+/**
+ * Bun-compat shim tests (issue #704).
+ *
+ * Each public surface is exercised against the live runtime. When running
+ * under Bun the shim delegates to the native `Bun.*` primitives; when running
+ * under Node the shim's fallback path is exercised. The test only asserts the
+ * observable contract (text equality, written byte count, exit code parity)
+ * — it does not lock in implementation details that legitimately differ
+ * between the two paths.
+ */
+export {};

package/dist/utils/__tests__/timeout.test.d.ts

@@ -0,0 +1,12 @@
+/**
+ * Timeout-helper tests (issue #704).
+ *
+ * The plugin init path uses `withTimeout` to bound the snapshot rehydration
+ * read so a slow filesystem cannot pin the host's `await server(...)`. The
+ * helper must:
+ *   - resolve to the racer's value when the racer wins,
+ *   - reject with the supplied error when the deadline elapses,
+ *   - clear its timer in `finally` (no leak that holds the loop open),
+ *   - never throw synchronously.
+ */
+export {};

package/dist/utils/bun-compat.d.ts

@@ -0,0 +1,106 @@
+/**
+ * Runtime-portability shim for the small set of `Bun.*` APIs we depend on.
+ *
+ * Why this exists: the plugin entry (`src/index.ts`) is bundled with
+ * `--target node`, but the source tree calls `Bun.file`, `Bun.write`,
+ * `Bun.spawn`, `Bun.spawnSync`, and `Bun.hash` directly. OpenCode's plugin
+ * host explicitly supports running plugins under Node (its own `PluginInput`
+ * uses `$: typeof Bun === "undefined" ? undefined : Bun.$`). On the OpenCode
+ * Desktop sidecar, plugins may execute under Node — every direct `Bun.*`
+ * reference would throw `ReferenceError: Bun is not defined`.
+ *
+ * This module funnels all such calls through a small set of helpers that
+ * detect the runtime once and dispatch to either the Bun primitive or a
+ * Node fallback. The fallbacks are deliberately small — they implement
+ * exactly the surface our callers use, no more.
+ *
+ * Cross-platform notes:
+ *   - `bunWrite` performs an atomic write via temp+rename on the Node path,
+ *     mirroring Bun's atomic semantics. Includes a Windows EEXIST retry loop
+ *     because rename can race with file-handle release on Windows.
+ *   - `bunSpawn` and `bunSpawnSync` use `node:child_process` and translate
+ *     Bun's option shape into Node's. Stdout/stderr capture is wired so
+ *     callers see the same `text()`/`stdout` shape regardless of runtime.
+ *   - `bunHash` uses Node's `xxhash` via `Bun.hash`'s default algorithm when
+ *     present and falls back to a stable djb2-derived 32-bit hash on Node.
+ */
+/**
+ * Whether the current runtime is Bun. Cached at first call — every subsequent
+ * call is a single property access.
+ */
+export declare function isBun(): boolean;
+/**
+ * Bun.file / fs read shim. Returns an object exposing the subset of
+ * `BunFile` methods used in this codebase: `text()`, `arrayBuffer()`,
+ * `exists()`, and `size`.
+ *
+ * On Bun, this is a thin wrapper around `Bun.file()` so callers see
+ * identical semantics. On Node, the methods read the file lazily.
+ */
+export interface BunCompatFile {
+    text(): Promise<string>;
+    arrayBuffer(): Promise<ArrayBuffer>;
+    exists(): Promise<boolean>;
+    readonly size: number;
+}
+export declare function bunFile(filePath: string): BunCompatFile;
+/**
+ * Atomic file write. On Bun this delegates to `Bun.write`. On Node we write
+ * to a temp file in the same directory and rename atomically — the same
+ * semantics every existing call site already expects via Bun.write.
+ */
+export declare function bunWrite(filePath: string, data: string | Uint8Array | ArrayBuffer | ArrayBufferView): Promise<number>;
+/**
+ * Stable 32-bit hash. Bun's `Bun.hash` uses xxHash64 by default; on Node we
+ * fall back to a 32-bit djb2 hash — identical hashes are NOT guaranteed
+ * across runtimes, so callers should not rely on cross-runtime hash equality
+ * (no current caller does — every `Bun.hash` use is in-process state keying
+ * or a same-runtime cache key).
+ */
+export declare function bunHash(input: string | ArrayBufferView | ArrayBuffer): bigint;
+/**
+ * Process spawn. Bun's `Bun.spawn` returns an object with `exited`, `stdout`,
+ * `stderr` etc. We expose a minimal compatible surface that callers actually
+ * use: `exited`, `exitCode`, and `stdout`/`stderr` as `ReadableStream`-like
+ * objects with `text()` and `bytes()` methods.
+ */
+export interface BunCompatSpawnOptions {
+    cwd?: string;
+    env?: Record<string, string | undefined>;
+    stdin?: 'inherit' | 'ignore' | 'pipe';
+    stdout?: 'inherit' | 'ignore' | 'pipe';
+    stderr?: 'inherit' | 'ignore' | 'pipe';
+    timeout?: number;
+}
+export interface BunCompatStream {
+    text(): Promise<string>;
+    bytes(): Promise<Uint8Array>;
+    /**
+     * Returns a Web ReadableStream reader for incremental, bounded
+     * consumption — matches the Bun runtime's `proc.stdout.getReader()`
+     * shape, used by the test-runner's `readBoundedStream` to cap memory
+     * for multi-GB test output.
+     */
+    getReader(): ReadableStreamDefaultReader<Uint8Array>;
+}
+export interface BunCompatSubprocess {
+    readonly stdout: BunCompatStream;
+    readonly stderr: BunCompatStream;
+    readonly exited: Promise<number>;
+    exitCode: number | null;
+    kill(signal?: NodeJS.Signals | number): void;
+}
+export declare function bunSpawn(cmd: string[], options?: BunCompatSpawnOptions): BunCompatSubprocess;
+export interface BunCompatSyncResult {
+    stdout: Uint8Array;
+    stderr: Uint8Array;
+    exitCode: number;
+    success: boolean;
+}
+export declare function bunSpawnSync(cmd: string[] | {
+    cmd: string[];
+    cwd?: string;
+    env?: Record<string, string | undefined>;
+    stdin?: string | Uint8Array;
+    timeout?: number;
+}, options?: BunCompatSpawnOptions): BunCompatSyncResult;

package/dist/utils/timeout.d.ts

@@ -0,0 +1,23 @@
+/**
+ * Timeout primitives used by the plugin init path.
+ *
+ * Hard rule: every timer scheduled here must call `unref()` so it never holds
+ * the process open, and every Promise.race must clear the timer in `finally`
+ * so it does not leak the timer reference after the racer settles.
+ */
+/**
+ * Race a promise against a timeout. The timer is cleared in `finally` so the
+ * Node event loop is not pinned open after the race resolves. The returned
+ * promise resolves to the racer's value, or rejects with the supplied
+ * `timeoutError` if the deadline elapses first.
+ *
+ * @param promise        Long-running operation to race.
+ * @param ms             Deadline in milliseconds.
+ * @param timeoutError   Error thrown when the deadline elapses.
+ */
+export declare function withTimeout<T>(promise: Promise<T>, ms: number, timeoutError: Error): Promise<T>;
+/**
+ * Yield to the macrotask queue. Works under both Node and Bun runtimes,
+ * unlike `setImmediate` which is Node-only.
+ */
+export declare function yieldToEventLoop(): Promise<void>;

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "opencode-swarm",
-	"version": "7.0.1",
+	"version": "7.0.3",
 	"description": "Architect-centric agentic swarm plugin for OpenCode - hub-and-spoke orchestration with SME consultation, code generation, and QA review",
 	"main": "dist/index.js",
 	"types": "dist/index.d.ts",
@@ -45,7 +45,8 @@
 		"format": "biome format . --write",
 		"check": "biome check --write .",
 		"dev": "bun run build && opencode",
-		"prepublishOnly": "bun run build"
+		"prepublishOnly": "bun run build",
+		"repro:704": "node scripts/repro-704.mjs"
 	},
 	"dependencies": {
 		"@opencode-ai/plugin": "^1.1.53",

package/dist/agents/council-member.d.ts

@@ -1,30 +0,0 @@
-/**
- * General Council member agent.
- *
- * Implements the NSED peer-review protocol (arXiv:2601.16863):
- *   - Round 1: independent search + answer with self-reported confidence
- *   - Round 2: targeted deliberation on disagreements with explicit MAINTAIN /
- *              CONCEDE / NUANCE stance (ConfMAD)
- *
- * Tools: web_search ONLY. No write tools, no orchestration tools. The architect
- * spawns members in parallel via the OpenCode subagent task system, collects
- * structured JSON responses, and synthesizes via convene_general_council.
- *
- * Prompt template variables (substituted by the architect at delegation time):
- *   {{MEMBER_ID}}         — the council member identifier
- *   {{ROLE}}              — generalist | skeptic | domain_expert | devil_advocate | synthesizer
- *   {{PERSONA_BLOCK}}     — optional persona instructions (omitted if undefined)
- *   {{ROUND}}             — "1" or "2"
- *   {{DISAGREEMENT_BLOCK}} — Round 2 only: opposing position(s) to address
- */
-import type { AgentDefinition } from './architect';
-export declare const COUNCIL_MEMBER_PROMPT = "You are Council Member {{MEMBER_ID}} ({{ROLE}}) on a multi-model General Council.\n\n{{PERSONA_BLOCK}}\n\nYou are participating in Round {{ROUND}} of a structured deliberation. Your job is to give your independent, evidence-grounded perspective \u2014 not to agree with the group.\n\n================================================================\nROUND {{ROUND}} PROTOCOL\n================================================================\n\nROUND 1 \u2014 Independent Research and Answer\n- Issue 1\u20133 targeted web_search calls to gather evidence relevant to the question.\n- Cite EVERY factual claim with a source URL from your search results.\n- State your confidence (0.0\u20131.0) explicitly. Be honest \u2014 overconfident answers hurt the council.\n- Enumerate areas of uncertainty so the architect knows where you're guessing vs. where you're sure.\n- Do NOT coordinate with other members. You will not see their responses until Round 2.\n- Do NOT pad. Be concise. Substance over volume.\n\nROUND 2 \u2014 Targeted Deliberation (ONLY when this round is invoked for you)\n- {{DISAGREEMENT_BLOCK}}\n- Issue at most 1 additional web_search call.\n- Declare your stance explicitly using one of these keywords as the FIRST word of a paragraph:\n    MAINTAIN  \u2014 your Round 1 position holds; cite the new evidence supporting it\n    CONCEDE   \u2014 the opposing position is correct; state specifically what you got wrong\n    NUANCE    \u2014 both positions are partially right; state the boundary condition that distinguishes them\n- Never CONCEDE without evidence. Sycophantic capitulation degrades the council below an individual member's baseline (NSED arXiv:2601.16863).\n- Never MAINTAIN without engaging the opposing argument on its merits.\n\n================================================================\nRESPONSE FORMAT (always \u2014 both rounds)\n================================================================\n\nReply with a single fenced JSON block. No prose outside the block.\n\n```json\n{\n  \"memberId\": \"{{MEMBER_ID}}\",\n  \"role\": \"{{ROLE}}\",\n  \"round\": {{ROUND}},\n  \"response\": \"Your full answer (Round 1) or stance + reasoning (Round 2). Markdown OK inside the string.\",\n  \"searchQueries\": [\"query 1\", \"query 2\"],\n  \"sources\": [\n    { \"title\": \"...\", \"url\": \"...\", \"snippet\": \"...\", \"query\": \"...\" }\n  ],\n  \"confidence\": 0.85,\n  \"areasOfUncertainty\": [\n    \"What I'm not sure about, in plain language.\"\n  ],\n  \"disagreementTopics\": []\n}\n```\n\nFor Round 1: leave `disagreementTopics` as []. For Round 2: list the specific disagreement topics this response addresses.\n\n================================================================\nHARD RULES\n================================================================\n- web_search is your ONLY tool. You cannot read or write files, run commands, or delegate.\n- Never invent sources. If a search returns nothing useful, say so in `areasOfUncertainty`.\n- Never echo other members' responses verbatim. Paraphrase or quote with attribution.\n- Stay within your role and persona. The architect chose you for a specific perspective.\n";
-/**
- * Factory for the council_member agent definition. The factory mirrors other
- * agent factories (createSMEAgent, createReviewerAgent) for consistency.
- *
- * Per-member context (memberId, role, persona, round, disagreement) is supplied
- * by the architect at delegation time via prompt-string substitution; the
- * factory itself produces the unparameterized template.
- */
-export declare function createCouncilMemberAgent(model: string, customPrompt?: string, customAppendPrompt?: string): AgentDefinition;

package/dist/agents/council-member.test.d.ts

@@ -1,8 +0,0 @@
-/**
- * Tests for src/agents/council-member.ts and src/agents/council-moderator.ts.
- *
- * Covers prompt template content (NSED protocol markers), AGENT_TOOL_MAP
- * enforcement (web_search-only for member, empty for moderator), and the
- * persona-block insertion path.
- */
-export {};

package/dist/agents/council-moderator.d.ts

@@ -1,20 +0,0 @@
-/**
- * General Council moderator agent.
- *
- * Receives the structural synthesis output from convene_general_council
- * (consensus / disagreements / sources) and produces a coherent, well-structured
- * final answer for the user. Empty tool list — moderation is synthesis-only;
- * it does NOT need web_search because every claim it works with has already
- * been searched and cited by council members.
- *
- * Confidence-weighted (Quadratic Voting from NSED arXiv:2601.16863): higher-
- * confidence members carry more weight, but evidence quality matters more
- * than confidence alone. The moderator must NOT favor a position purely
- * because its proponent was confident.
- */
-import type { AgentDefinition } from './architect';
-export declare const COUNCIL_MODERATOR_PROMPT = "You are the General Council Moderator.\n\nYou are receiving the structural synthesis from a multi-model council deliberation:\n- Question (and mode: general or spec_review)\n- All member Round 1 responses with sources\n- Detected disagreements\n- Round 2 deliberation responses (if any)\n- Confidence-weighted consensus claims\n- Persisting disagreements after deliberation\n\nYour job: produce a coherent, well-structured final answer for the user.\n\n================================================================\nRULES\n================================================================\n\n1. LEAD WITH CONSENSUS \u2014 open with the strongest consensus position. Use the\n   confidence-weighted ordering (Quadratic Voting): higher-confidence claims\n   from multiple members rank higher, but evidence quality outranks raw\n   confidence. Never elevate a single confident voice over a well-evidenced\n   contrary majority.\n\n2. ACKNOWLEDGE DISAGREEMENT HONESTLY \u2014 for each persisting disagreement, write\n   \"experts disagree on X because\u2026\" and present the strongest version of each\n   side. Do NOT pretend disagreements are resolved when they are not. Do NOT\n   silently pick a winner.\n\n3. CITE THE STRONGEST SOURCES \u2014 link key claims with [title](url) format from\n   the deduplicated source list. Pick the most reputable source for each claim;\n   do not cite duplicates.\n\n4. BE CONCISE \u2014 the user wants an answer, not a committee report. Default\n   length: a few short paragraphs plus a bulleted summary. Expand only when\n   the question genuinely requires it.\n\n================================================================\nHARD CONSTRAINTS\n================================================================\n\n- You MUST NOT invent claims that are not present in the council's responses.\n- You MUST NOT add new web research. If something was missed, say so.\n- You MUST NOT favor a position based on member confidence alone \u2014 evidence\n  quality is the tie-breaker.\n- You have NO tools. You write the final synthesis from the input given.\n\n================================================================\nOUTPUT FORMAT\n================================================================\n\nPlain markdown. No code fences. No JSON. Suggested structure:\n\n# Answer\n\n<lead consensus position with citation(s)>\n\n<remaining consensus / context paragraphs as needed>\n\n## Where Experts Disagree\n\n- <topic 1>: <position A> vs <position B>, with sources for each\n- <topic 2>: ...\n\n## Sources\n\n- [title](url)\n- ...\n\n(Omit any section that is empty.)\n";
-/**
- * Factory for the council_moderator agent definition. No tools — synthesis only.
- */
-export declare function createCouncilModeratorAgent(model: string, customPrompt?: string, customAppendPrompt?: string): AgentDefinition;