opencode-swarm 7.129.3 → 7.129.4

package/dist/services/directive-predicate-runner.d.ts

@@ -47,6 +47,9 @@ export declare const TOOL_BINARY_ALLOWLIST: ReadonlySet<string>;
  * `{}`) are permitted; traversal and absolute paths are not.
  */
 export declare function validateRepoRelativeGlob(directory: string, value: string): string | null;
+/** Find a binary on PATH (Bun.which misses runtime PATH changes).
+ *  On Windows, checks .exe, .cmd, .bat, and bare name (issue #1691). */
+declare function findBinaryInPath(binary: string): string | null;
 interface RunResult {
     exitCode: number | null;
     stdout: string;
@@ -69,4 +72,7 @@ export declare const _internals: {
     runDirectivePredicate: typeof runDirectivePredicate;
     TOOL_BINARY_ALLOWLIST: ReadonlySet<string>;
 };
+export declare const _test_exports: {
+    findBinaryInPath: typeof findBinaryInPath;
+};
 export {};

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "opencode-swarm",
-	"version": "7.129.3",
+	"version": "7.129.4",
 	"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",

package/dist/config/loader-recovery.d.ts

@@ -1,95 +0,0 @@
-/**
- * Config loader recovery persistence module.
- *
- * Persists recovery metadata emitted by the config loader so that:
- *   - `/swarm config doctor` can surface stale recovery artifacts
- *     (left by a prior process that crashed before cleanup).
- *   - Post-init flush (via `flushPendingLoaderRecovery`) can record
- *     recovery warnings without blocking plugin init.
- *   - Stale artifacts from older loads are cleaned up atomically
- *     when a newer load completes successfully (SC-002.3).
- *
- * Conflict resolution: every completed load writes a recovery artifact
- * tagged with the tuple `{loadStartedAt, pid, inProcessCounter}`. When
- * an artifact already exists, the new load wins iff its tuple is
- * numerically greater than the existing one (component-wise comparison).
- * This prevents a slower or earlier process from overwriting a newer
- * recovery result.
- *
- * Artifact format (JSON):
- * ```json
- * {
- *   "loadStartedAt": number,
- *   "pid": number,
- *   "inProcessCounter": number,
- *   "sources": string[],
- *   "fingerprint": string,
- *   "warnings": RecoveryWarning[]
- * }
- * ```
- *
- * Lives under `src/config/` alongside `loader.ts` so the loader can
- * import it without cross-module dependency violations.
- */
-import * as fsPromises from 'node:fs/promises';
-import { bunWrite } from '../utils/bun-compat.js';
-import type { RecoveryWarning } from './sanitize-malformed-values.js';
-/** Shape of the on-disk recovery artifact. */
-export interface LoaderRecoveryArtifact {
-    /** Date.now() when the config load started. */
-    loadStartedAt: number;
-    /** process.pid of the loading process. */
-    pid: number;
-    /** Monotonic per-process counter for same-process disambiguation. */
-    inProcessCounter: number;
-    /** Sorted source paths that contributed to the config merge. */
-    sources: string[];
-    /** SHA-256 fingerprint of the merged raw config. */
-    fingerprint: string;
-    /** Recovery warnings from the load (empty for clean loads). */
-    warnings: RecoveryWarning[];
-}
-/**
- * Input shape accepted by the public API.
- * Matches `LoadPluginConfigWithRecoveryResult.pendingPersistence`
- * from `loader.ts`.
- */
-export type PendingLoaderRecoveryData = Omit<LoaderRecoveryArtifact, 'warnings'> & {
-    warnings: RecoveryWarning[];
-};
-/**
- * Test-only dependency-injection seam — replaces `fsPromises.readFile`
- * and `bunWrite` so tests can exercise failure paths without
- * `mock.module` leakage (AGENTS.md §7).
- */
-export declare const _internals: {
-    readFile: typeof fsPromises.readFile;
-    write: typeof bunWrite;
-};
-/**
- * Persist loader recovery data to `<directory>/.swarm/advisories/loader-recovery.json`.
- *
- * Every completed load atomically writes the artifact under deterministic
- * conflict resolution: the new load wins iff its `{loadStartedAt, pid,
- * inProcessCounter}` tuple is numerically greater than the existing artifact's.
- * Clean loads (no recovery warnings) write `warnings: []`, which serves as
- * the SC-002.3 stale-artifact cleanup signal.
- *
- * Failures (filesystem errors, permission issues) are logged via
- * `advisoryWarn` and never thrown — this is best-effort persistence.
- *
- * @param directory - Project root directory (the `.swarm/` parent).
- * @param data - Recovery data from the loader's `pendingPersistence`.
- */
-export declare function persistLoaderRecovery(directory: string, data: PendingLoaderRecoveryData): Promise<void>;
-/**
- * Synchronous wrapper that defers `persistLoaderRecovery` via `queueMicrotask`.
- *
- * This is designed for the post-init flush path (task 1.5) where the caller
- * must not await the write — the write is fire-and-forget, with errors
- * routed to `advisoryWarn` inside `persistLoaderRecovery`.
- *
- * @param directory - Project root directory (the `.swarm/` parent).
- * @param pendingData - Recovery data from the loader's `pendingPersistence`.
- */
-export declare function flushPendingLoaderRecovery(directory: string, pendingData: PendingLoaderRecoveryData): void;