@sleep2agi/agent-network 2.3.0-preview.11 → 2.3.0-preview.111

package/dist/src/im/types.d.ts

@@ -72,13 +72,42 @@ export interface NormalizedIMEvent {
     mentioned: boolean;
     content: {
         text?: string;
-        /** Local filesystem paths to already-downloaded images. */
+        /** Local filesystem paths to already-downloaded images.
+         *
+         *  RFC-020 §17 backward-compat shim: the new richer
+         *  `attachments[]` field below is the canonical source going
+         *  forward. `images` stays a `string[]` of paths so an older
+         *  agent-node worker reading this envelope across a rolling
+         *  upgrade doesn't crash. New workers prefer `attachments`,
+         *  old workers ignore it and keep using `images`. */
         images?: string[];
         files?: {
             name: string;
             path?: string;
             url?: string;
         }[];
+        /** RFC-020 §17 cross-machine attachment descriptors.
+         *
+         *  Each entry mirrors `meta.attachments[]` on commhub tasks
+         *  (`{ type, file_id?, path?, mime?, name?, size? }`). The
+         *  feishu bridge populates `file_id` by uploading inbound
+         *  files to `/api/upload` so cross-host agents delegated via
+         *  `commhub_send_task(meta.attachments=...)` can fetch via
+         *  `/api/files/<id>`. When upload fails, `file_id` is absent
+         *  and the descriptor degrades to path-only (single-host
+         *  still works via local Read; no regression vs pre-fix
+         *  baseline).
+         *
+         *  Always populated alongside `images` for the same files —
+         *  duplication is intentional for rolling-upgrade safety. */
+        attachments?: Array<{
+            type: "image" | "file";
+            path?: string;
+            file_id?: string;
+            mime?: string;
+            name?: string;
+            size?: number;
+        }>;
     };
     /**
      * Original platform payload. Default: held in memory only and dropped after

package/dist/src/inbox-drain.d.ts

@@ -0,0 +1,20 @@
+export interface InboxPage<T> {
+    ok?: boolean;
+    messages?: T[];
+}
+export interface DrainOptions<T extends {
+    id: string;
+}> {
+    fetchPage: (limit: number) => Promise<InboxPage<T> | undefined | null>;
+    handle: (msg: T) => Promise<void>;
+    pageSize?: number;
+    maxPages?: number;
+}
+export interface DrainResult {
+    delivered: number;
+    pages: number;
+    stoppedBy: "empty" | "short-page" | "max-pages" | "no-progress" | "fetch-error";
+}
+export declare function drainInbox<T extends {
+    id: string;
+}>(opts: DrainOptions<T>): Promise<DrainResult>;

package/dist/src/local-process-state.d.ts

@@ -0,0 +1,12 @@
+export type LocalProcessState = {
+    kind: "alive";
+    pid: number;
+} | {
+    kind: "stale";
+    pid: number;
+} | {
+    kind: "none";
+};
+export declare function describeLocalProcess(state: LocalProcessState): string;
+/** doctor 印完节点清单后的那一句:说清这一列量的是本机,不是 hub。 */
+export declare const LOCAL_VS_HUB_NOTE: string;

package/dist/src/locale-diagnostic.d.ts

@@ -0,0 +1,12 @@
+export interface LocaleDiagnostic {
+    effectiveVariable: "LC_ALL" | "LC_CTYPE" | "LANG" | null;
+    effectiveValue: string | null;
+    shouldWarn: boolean;
+}
+/**
+ * Resolve the locale with the same precedence used by POSIX libc. Windows
+ * does not use these variables as its process Unicode boundary, so prescribing
+ * a POSIX locale there would be misleading.
+ */
+export declare function diagnoseLocale(env: Readonly<Record<string, string | undefined>>, platform: string): LocaleDiagnostic;
+export declare function formatLocaleSource(diagnostic: LocaleDiagnostic): string;

package/dist/src/ls-columns.d.ts

@@ -0,0 +1,15 @@
+/**
+ * 一列该多宽:装得下表头,也装得下这一列里最长的那个值。
+ *
+ * 🔴 两处用它的地方来源不同,但问题一样:
+ *  - `anet node ls` 的 RUNTIME 列:值域来自 `SUPPORTED_RUNTIME_NAMES`(唯一真源);
+ *  - `anet status` / `anet tasks` 的 STATUS 列:值域散在 server/ 里(另一个包),
+ *    CLI 没法 import —— 但**要打印的那些行就在手上**,直接从数据算。
+ *
+ * 两种情况都不该写死一个数:写死的那个,下一次加 runtime / 加状态时就漂了。
+ */
+export declare function columnWidth(values: readonly unknown[], header: string): number;
+/** RUNTIME 列的专用入口 —— 保留原名,调用点不用改。 */
+export declare function runtimeColumnWidth(names: readonly string[], header?: string): number;
+export declare function lsHeaderRow(runtimeWidth: number): string;
+export declare function lsSeparatorRow(runtimeWidth: number): string;

package/dist/src/mock-llm.d.ts

@@ -0,0 +1,12 @@
+export declare const MOCK_LLM_FALLBACK = "(mock LLM: no rule matched)";
+export type MockLlmRule = Readonly<{
+    in_substring: string;
+    out: string;
+}>;
+export type MockLlmResolution = Readonly<{
+    reply: string;
+    matched: boolean;
+    ruleIndex: number | null;
+}>;
+export declare function loadMockLlmRules(path: string): readonly MockLlmRule[];
+export declare function resolveMockLlmReply(rules: readonly MockLlmRule[], prompt: string, warn?: (message: string) => void): MockLlmResolution;

package/dist/src/node-activity-log.d.ts

@@ -0,0 +1,4 @@
+export interface ActivityLogSink {
+    append(line: string): void;
+}
+export declare function createActivityLogSink(baseDir: string, alias: string, now?: () => Date): ActivityLogSink;

package/dist/src/node-not-found.d.ts

@@ -0,0 +1 @@
+export declare function nodeNotFoundMessage(ref: string, knownNames: string[], suggestion: string | null): string;

package/dist/src/node-running-guard.d.ts

@@ -0,0 +1,9 @@
+export declare const isAgentNodeCommand: (cmdline: string) => boolean;
+export interface RunningNodeProbe {
+    pidFileContent: string | null;
+    isAlive: (pid: number) => boolean;
+    commandOf: (pid: number) => string | null;
+}
+/** 返回还活着且确实是 agent-node 的 pid;否则 null(不存在 / 死了 / pid 被别的进程复用)。 */
+export declare const runningNodePid: (probe: RunningNodeProbe) => number | null;
+export declare const alreadyRunningMessage: (displayName: string, pid: number) => string[];

package/dist/src/node-server-payload.d.ts

@@ -0,0 +1,66 @@
+/**
+ * What gets written to `<project>/.anet/node-server.js` (issue #1216).
+ *
+ * The target name is not negotiable: `agent-node`'s grok co-presence spawn
+ * gate pins the CommHub MCP payload to exactly that path, so whatever the
+ * source is, the file that lands there is called `.js`.
+ *
+ * 🔴 The bug this module exists to remove: the old code copied the source
+ * verbatim and justified it with a comment claiming
+ *
+ *     "bun runs .ts content under a .js extension fine"
+ *
+ * which is false — bun selects its parser from the extension:
+ *
+ *     $ printf 'function f(x: string): void {}\nf("hi");\n' > probe.ts
+ *     $ cp probe.ts probe.js
+ *     $ bun probe.ts   → runs
+ *     $ bun probe.js   → error: Expected ")" but found ":"
+ *
+ * An installed npm package never hit it, because its first resolver candidate
+ * (`dist/src/node-server.js`) is compiled. Only a source checkout fell through
+ * to `src/node-server.ts` — i.e. every local run and every hand-verified PR.
+ *
+ * And the symptom was three layers from the cause: the node died on
+ * `grok copresence CommHub MCP readiness preflight failed (1)`, which names
+ * neither a file nor a parse error.
+ */
+/** Injected so the decision is testable without spawning anything. */
+export interface TypeScriptBundler {
+    /** Returns the self-contained JavaScript for `entryPath`, or throws. */
+    bundleSync(entryPath: string): string;
+}
+export declare class NodeServerPayloadError extends Error {
+    constructor(message: string);
+}
+/**
+ * Decide what bytes belong at the `.js` target for a given source path.
+ *
+ * A `.js` source is passed through untouched — the published package ships a
+ * compiled bundle there, and re-processing it risks changing bytes for no gain.
+ *
+ * 🔴 A `.ts` source must be **bundled, not merely transpiled**. Stripping types
+ * fixes the parse error but leaves the file's relative imports pointing at
+ * siblings that do not exist beside the destination:
+ *
+ *     import { inboundChannelMeta } from "./channel-meta.js";
+ *     → Cannot find module './channel-meta.js' from '<project>/.anet/node-server.js'
+ *
+ * That second failure is why transpiling alone still ended at
+ * "CommHub MCP readiness preflight failed (1)". The published
+ * `dist/src/node-server.js` works precisely because it is a self-contained
+ * bundle, so a source checkout has to produce the same shape.
+ */
+export declare function nodeServerPayloadFor(source: string, sourcePath: string, bundler: TypeScriptBundler | null): string;
+/**
+ * The bundler available on this runtime, or null.
+ *
+ * bun can bundle; the published CLI runs under node and cannot — but it also
+ * never resolves a `.ts` candidate (its `dist/` copy wins), so null there is
+ * correct rather than a gap.
+ *
+ * `spawnSync` rather than `Bun.build()` because both call sites are
+ * synchronous, and making them async would change the ordering of the file
+ * writes around them.
+ */
+export declare function ambientTypeScriptTranspiler(): TypeScriptBundler | null;

package/dist/src/node-server-rules-file.d.ts

@@ -0,0 +1,12 @@
+export declare const CLAUDE_CODE_RULES_RUNTIME = "claude";
+export interface RulesDoorbellDeps {
+    callCommHub: (method: string, params: Record<string, unknown>) => Promise<any>;
+    workDir: string;
+    log: (msg: string) => void;
+}
+/** SSE 事件分派:是 rules_file 门铃就处理并返回 true;其它事件原样返回 false。 */
+export declare function handleRulesFileEvent(event: {
+    type?: unknown;
+} | null | undefined, deps: RulesDoorbellDeps): Promise<boolean>;
+/** 连上 / 重连后补拉一次:断线期间桌面端可能已发起请求(hub 侧 60s 内仍 pending)。 */
+export declare function drainRulesFileRequests(deps: RulesDoorbellDeps, why: string): Promise<number>;