@sleep2agi/agent-network 2.3.0-preview.64 → 2.3.0-preview.66

package/dist/src/opencode-agent-node-pair.d.ts

@@ -1,9 +1,9 @@
-export declare const PAIRED_AGENT_NETWORK_VERSION = "2.3.0-preview.64";
-export declare const PAIRED_AGENT_NODE_VERSION = "2.5.0-preview.49";
-export declare const PAIRED_AGENT_NODE_SPEC = "@sleep2agi/agent-node@2.5.0-preview.49";
-export declare const OPENCODE_AGENT_NETWORK_VERSION = "2.3.0-preview.64";
-export declare const OPENCODE_AGENT_NODE_VERSION = "2.5.0-preview.49";
-export declare const OPENCODE_AGENT_NODE_SPEC = "@sleep2agi/agent-node@2.5.0-preview.49";
+export declare const PAIRED_AGENT_NETWORK_VERSION = "2.3.0-preview.66";
+export declare const PAIRED_AGENT_NODE_VERSION = "2.5.0-preview.51";
+export declare const PAIRED_AGENT_NODE_SPEC = "@sleep2agi/agent-node@2.5.0-preview.51";
+export declare const OPENCODE_AGENT_NETWORK_VERSION = "2.3.0-preview.66";
+export declare const OPENCODE_AGENT_NODE_VERSION = "2.5.0-preview.51";
+export declare const OPENCODE_AGENT_NODE_SPEC = "@sleep2agi/agent-node@2.5.0-preview.51";
 export type PairedAgentNodeResolution = {
     spec: string;
     args: string[];

package/dist/src/package-mode-preflight.d.ts

@@ -14,8 +14,18 @@ export interface UmaskVerdict {
  * nothing else, which is exactly the failing case.
  */
 export declare function judgeUmask(umask: number): UmaskVerdict;
-/** One line for `anet doctor`, or null when there is nothing to say. */
-export declare function describeUmaskRisk(verdict: UmaskVerdict): string | null;
+/**
+ * One line for `anet doctor`, or null when there is nothing to say.
+ *
+ * 🔴 Windows gets a different sentence, not the same one. There, umask is always
+ *    0000 and this fires on every machine, while both remedies it names —
+ *    `umask 0022` and `chmod -R` — do not exist. The conclusion is still true
+ *    (opencode-cli will refuse), but for another reason entirely: its check is
+ *    `if (runtimeUid === undefined) return false`, and Windows has no getuid.
+ *    An always-on warning whose fix cannot be typed teaches people to ignore
+ *    the warnings that can be.
+ */
+export declare function describeUmaskRisk(verdict: UmaskVerdict, platform?: NodeJS.Platform): string | null;
 export interface ExtractedPayload {
     path: string;
     uid: number;

package/dist/src/posix-modes.d.ts

@@ -0,0 +1,36 @@
+export declare function posixFileModes(platform?: NodeJS.Platform): boolean;
+/** chmod where the platform has modes; a no-op where it does not. */
+export declare function chmodIfPosix(path: string, mode: number): void;
+/** fchmod where the platform has modes; a no-op where it does not. */
+export declare function fchmodIfPosix(fd: number, mode: number): void;
+/**
+ * Whether a stat's mode may be judged at all.
+ *
+ * Windows synthesises mode bits, so `(mode & 0o022) !== 0` is true for ordinary
+ * files there and every POSIX-shaped safety check reads as "unsafe". A check
+ * that can only ever return one answer is not a check.
+ */
+export declare function modeIsJudgeable(platform?: NodeJS.Platform): boolean;
+/**
+ * fsync a DIRECTORY handle, where the platform supports it.
+ *
+ * The durability barrier after an atomic rename: on POSIX, fsyncing the parent
+ * makes the rename itself survive a crash, not just the file's bytes. Windows
+ * has no equivalent — FlushFileBuffers works on files, and on a directory
+ * handle it fails:
+ *
+ *     [anet] FATAL: Error: EPERM: operation not permitted, fsync
+ *         at fsyncSync (node:fs:1285:11)
+ *
+ * which is `anet start <node>` dying on its first private-state write. Reported
+ * from the Windows box while it was running the previous fix, i.e. this is the
+ * next call in the same family, not a regression of that one.
+ *
+ * 🔴 Note what is NOT skipped: the fsync of the temp FILE before the rename.
+ *    That one works on Windows and carries the bytes. What is skipped is only
+ *    the parent-directory barrier, which the platform does not offer at all —
+ *    NTFS journals the rename's metadata itself. Skipping an operation the OS
+ *    cannot perform is not a weakened guarantee; crashing instead of writing
+ *    the file is a much larger one.
+ */
+export declare function fsyncDirectoryIfSupported(fd: number): void;

package/dist/src/profile-serialize.d.ts

@@ -0,0 +1 @@
+export declare function serializeProfileForConfigJson(normalized: Record<string, any>, profile: Record<string, any>): Record<string, any>;

package/dist/src/tool-allowlist.d.ts

@@ -0,0 +1,28 @@
+export declare const CLAUDE_KNOWN_TOOLS: readonly string[];
+type Runtime = string;
+/** Parse the comma-joined --tools string, validate each token, return the
+ * trimmed list. Runtime-scoped:
+ *
+ *   Claude-lineage → each token must be in CLAUDE_KNOWN_TOOLS OR match
+ *                    the MCP pattern (mcp__<server>__<tool>).
+ *   Other runtimes → only the basic per-token format check runs, so grok /
+ *                    codex / opencode tools flow through unchanged and get
+ *                    validated by their own downstream layers.
+ *
+ * Throws on the first offense with a message naming the bad token and,
+ * for Claude-side violations, the expected set. Never returns a
+ * partially-cleaned list — a typo must surface, not silently reshape the
+ * persisted profile.
+ */
+export declare function parseAndValidateTools(raw: string, runtime: Runtime): string[];
+/** Minimal --model validation: non-empty after trim, no whitespace inside.
+ *
+ * We do NOT enforce a known-model allowlist — models are vendor-defined,
+ * evolve independently, and a strict list would break the first time
+ * MiniMax/DeepSeek/GLM/etc. ships a new variant. This catches the obvious
+ * user-side typos (`--model " claude-3 " `, `--model ""`) without
+ * over-restricting legitimate values. Vendor-side model resolution
+ * (defaultCodexModelForRuntime etc.) already validates its own contract.
+ */
+export declare function validateModel(raw: string): string;
+export {};

package/dist/src/win-launcher.d.ts

@@ -0,0 +1,20 @@
+import { type ExecFileSyncOptions, type ExecFileSyncOptionsWithStringEncoding, type SpawnOptions } from "child_process";
+/** Windows needs a command interpreter to run a .cmd; POSIX runs the file. */
+export declare function launcherNeedsShell(platform?: NodeJS.Platform): boolean;
+/**
+ * Quote one argument for `cmd.exe /c`.
+ *
+ * cmd's rules are not the shell's: a double quote is escaped by doubling it,
+ * and the metacharacters below must be quoted or cmd will act on them. Anything
+ * safe is left bare, so the common case stays readable in a process listing.
+ */
+export declare function quoteForCmd(arg: string): string;
+/** The argv to hand to execFile/spawn so `cmd args…` runs on this platform. */
+export declare function launcherArgv(cmd: string, args: readonly string[], platform?: NodeJS.Platform, comspec?: string | undefined): {
+    file: string;
+    argv: string[];
+};
+export declare function runLauncherSync(cmd: string, args: readonly string[], options: ExecFileSyncOptionsWithStringEncoding): string;
+export declare function runLauncherSync(cmd: string, args: readonly string[], options?: ExecFileSyncOptions): Buffer;
+/** spawn for a launcher, correct on Windows. */
+export declare function spawnLauncher(cmd: string, args: readonly string[], options?: SpawnOptions): import("node:child_process").ChildProcess;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sleep2agi/agent-network",
-  "version": "2.3.0-preview.64",
+  "version": "2.3.0-preview.66",
   "description": "AI Agent Network CLI — Local-first multi-agent orchestration across 6 runtimes (Claude Code CLI / Claude Agent SDK / Codex SDK / Codex app-server / Grok Build ACP / OpenCode CLI) and 8+ LLM providers. Apache 2.0.",
   "type": "module",
   "main": "dist/src/client.js",