@sleep2agi/agent-network 2.3.0-preview.4 → 2.3.0-preview.41

package/dist/src/im/feishu/adapter.d.ts

@@ -1,12 +1,49 @@
+/**
+ * RFC-020 §3.1 — Feishu (Lark) adapter for the IM compatibility layer.
+ *
+ * Uses `@larksuiteoapi/node-sdk` in WebSocket long-connection mode (WSClient).
+ * No public IP / no domain verification / no webhook signature decryption —
+ * the three biggest 飞书 接入 risks all live in the HTTP event-callback path,
+ * not in WSClient mode.
+ *
+ * Milestones:
+ *   M1: contract scaffold.
+ *   M2 (this file): WSClient init + EventDispatcher for `im.message.receive_v1`
+ *                   + event normalization + access whitelist gate + audit log.
+ *   M3: outbound `im.message.create` (text), edit support (≤20/msg).
+ *   M5: image upload / download (`im.image.create` / `im.messageResource.get`)
+ *       + group @bot detection refined to match the bot's own open_id.
+ */
+import * as lark from "@larksuiteoapi/node-sdk";
 import type { IMAdapter, IMAdapterHealth, IMChannelConfig, IMConversationRef, IMIngressMode, NormalizedIMEvent, NormalizedIMMessage } from "../types.js";
 type OnEventHandler = (event: NormalizedIMEvent) => Promise<void>;
+export type FeishuWsClientLike = Pick<lark.WSClient, "start" | "close">;
+export type FeishuWsClientFactory = (params: ConstructorParameters<typeof lark.WSClient>[0]) => FeishuWsClientLike;
+type FeishuInboundHandler = (rawEvent: unknown) => Promise<unknown>;
+export interface FeishuEventDispatcherLike {
+    register(handlers: Record<string, FeishuInboundHandler>): unknown;
+}
+export interface FeishuAdapterOptions {
+    /** @internal Avoids real bot-info HTTP calls in lifecycle tests. */
+    createClient?: (params: ConstructorParameters<typeof lark.Client>[0]) => lark.Client;
+    /** @internal Test seam; production uses the pinned Lark SDK WSClient. */
+    createWsClient?: FeishuWsClientFactory;
+    /** @internal Test seam; production uses the pinned Lark SDK dispatcher. */
+    createEventDispatcher?: () => FeishuEventDispatcherLike;
+    /** Independent outer bound in case the SDK promise/callback path stalls. */
+    wsReadyTimeoutMs?: number;
+    /** Called once when an already-ready socket exhausts reconnect attempts. */
+    onTerminalError?: (error: Error) => void;
+}
 export declare class FeishuAdapter implements IMAdapter {
     readonly platform = "feishu";
     readonly ingressMode: IMIngressMode;
     private feishuConfig;
-    private connectionName;
+    private connectionName_;
     private client;
     private wsClient;
+    private lifecycleGeneration;
+    private readonly options;
     /**
      * The bot's own open_id, resolved at init() via /open-apis/bot/v3/info.
      * Used to detect real @bot mentions (vs any mention) in group messages.
@@ -17,6 +54,24 @@ export declare class FeishuAdapter implements IMAdapter {
     /** Where to persist downloaded inbound media (M5c). */
     private mediaDir;
     private health_;
+    constructor(options?: FeishuAdapterOptions);
+    /**
+     * Snapshot of the current `access.allowFrom` list (from access.json).
+     * Used by the bridge's rate-limiter to exempt operator-vouched explicit
+     * sender ids from the DM flood limit (2026-06-29: Vincent's multi-turn
+     * heavy work was tripping the 3-msg/60s DM limit; explicit-listed
+     * users are already operator-trusted via the access whitelist, no
+     * need to also flood-limit them). Returns `[]` before `init()`. The
+     * wildcard `["*"]` allowlist does NOT count as "explicit" — that's
+     * the public-channel shape and still needs flood protection.
+     */
+    getAllowFrom(): readonly string[];
+    /**
+     * Read-only accessor used by bridge to resolve per-connection paths
+     * (RFC-020 §15 outbound-marker validation needs the connection name
+     * to build the allowed per-conversation directory prefix).
+     */
+    get connectionName(): string;
     init(config: IMChannelConfig): Promise<void>;
     start(onEvent: OnEventHandler): Promise<void>;
     stop(): Promise<void>;
@@ -26,4 +81,97 @@ export declare class FeishuAdapter implements IMAdapter {
     edit(_target: IMConversationRef, messageId: string, message: NormalizedIMMessage): Promise<void>;
     health(): IMAdapterHealth;
 }
+/**
+ * Heuristic — does this text look like it contains markdown syntax that
+ * Feishu's plain-text `msg_type:"text"` would render as literal source?
+ * Catches the patterns Vincent's heavy work produces: tables (`|...|`
+ * + separator row), fenced code blocks (`` ``` ``), ATX headings (`#`),
+ * bold/italic (`**text**` / `*text*`), unordered/ordered lists, inline
+ * code (`` `code` ``), markdown links (`[label](url)`).
+ *
+ * Returns true for at least one match; the adapter then upgrades to
+ * `msg_type:"interactive"` with a `markdown` element. Returns false for
+ * plain prose so the text path stays untouched (no perf cost, no
+ * behavior change for non-markdown replies).
+ *
+ * Conservative — single-character matches (e.g., a `|` in prose, one
+ * `*` for emphasis-of-one-word that Feishu would render OK as text)
+ * are NOT enough to trigger. We want false-positives < false-negatives
+ * (a false-positive upgrade renders fine; a false-negative shows raw
+ * `|` and `**`).
+ */
+export declare function looksLikeMarkdown(text: string): boolean;
+/**
+ * Parse Feishu `message_type: "post"` content into plain text. Post
+ * content is a nested structure:
+ *
+ *   { title?: string,
+ *     content: Array<Array<{ tag: "text"|"img"|"a"|"at"|"emotion", ... }>>
+ *   }
+ *
+ * Each top-level array entry is a paragraph; each paragraph is an array
+ * of typed segments. We flatten by:
+ *   - prepending title (if present) as `<title>\n\n`
+ *   - joining paragraphs with `\n\n`
+ *   - joining segments within a paragraph in order
+ *   - tag=text → emit segment.text as-is
+ *   - tag=a    → emit `[label](href)` (markdown link)
+ *   - tag=at   → emit `@user_name` (fallback to `@<user_id>` if no name)
+ *   - tag=img  → emit `[图片]` placeholder (actual download via maybeAttachImages)
+ *   - tag=emotion → emit `[emoji]`
+ *   - unknown tag → skip
+ *
+ * @internal exported for unit tests.
+ */
+export declare function parsePostContent(rawJson: string): string;
+/**
+ * Walk a Feishu `post` content JSON and collect all `image_key` values
+ * from `tag: "img"` segments. Used by `maybeAttachImages` to schedule
+ * downloads for every image in a 图文混排 message.
+ *
+ * @internal exported for unit tests.
+ */
+export declare function extractPostImageKeys(rawJson: string): string[];
+/**
+ * Sanitize a Feishu-supplied `file_name` so it's safe to append to a
+ * filesystem path. Strips `/`, `\`, `..`, control characters, and NUL
+ * bytes. Empty / all-stripped input falls back to a placeholder that
+ * uses the message id, so a hostile client can never write outside the
+ * conversation's `<mediaDir>/<convKey>/` directory.
+ *
+ * NOT a full display-safety pass — the LLM still sees the sanitized
+ * bytes and shouldn't render them as HTML/etc. That's a Layer above.
+ */
+export declare function sanitizeFileName(raw: string, fallback: string): string;
+/**
+ * Feishu text-message practical chunk threshold (RFC-020 §16).
+ *
+ * The official `im.message.create`/`reply` content limit for
+ * `msg_type:text` is ~30 KB JSON-encoded (`{"text":"..."}`), comfortably
+ * under what any reasonable bot reply produces. We chunk below that
+ * limit at 4000 CHARACTERS — gives a roomy safety margin for multi-byte
+ * UTF-8 and lets us split at paragraph boundaries cleanly. Chosen
+ * conservatively after Vincent 2026-06-30 ask "issue 发文字" (i.e.
+ * never silently fall back to PNG for "long" plain-text replies — they
+ * just chunk into multiple messages).
+ *
+ * Single-message ceiling, NOT a per-second rate limit (that's separate;
+ * RFC-020 §4.4).
+ */
+export declare const FEISHU_TEXT_SINGLE_LIMIT = 4000;
+/**
+ * Split a long text into chunks ≤ `maxChars`. Tries paragraph boundaries
+ * (`\n\n`), then line boundaries (`\n`), then word boundaries (space),
+ * then hard byte split. Output preserves the original text content
+ * (sum of chunks == original, modulo the boundary character that gets
+ * consumed by the split).
+ *
+ * If the input is already short enough, returns a single-element array.
+ */
+export declare function splitTextForFeishu(text: string, maxChars: number): string[];
+/**
+ * Lark errors may echo request/config values. Keep worker logs actionable while
+ * ensuring credentials and multiline payloads never cross the process boundary.
+ */
+export declare function sanitizeFeishuWsError(rawError: unknown, appId: string, appSecret: string): Error;
 export {};

package/dist/src/im/feishu/bridge.d.ts

@@ -44,11 +44,20 @@ export interface FeishuBridgeOptions {
      *   - stderr logger otherwise (standalone smoke debugging).
      */
     onEvent?: (event: NormalizedIMEvent) => Promise<void>;
+    /** Fatal WS failure after initial readiness (for worker lifecycle ownership). */
+    onTerminalError?: (error: Error) => void;
 }
 /** Bridge → parent: inbound IM event ready for think(). */
 export interface BridgeIncomingEnvelope {
     type: "event";
     event: NormalizedIMEvent;
+    /** Canonical outbound directory for this conversation (RFC-020 §15.1).
+     *  Single source of truth — the agent-node injects this verbatim into
+     *  the system prompt's "save files here" instruction, and the bridge
+     *  whitelist accepts files only under this directory. Computed by the
+     *  bridge from `event.conversation.conversationId` + `adapter
+     *  .connectionName`. Trailing slash included. */
+    outboundDir?: string;
 }
 /** Parent → bridge: agent reply text for a previously-forwarded event. */
 export interface BridgeReplyEnvelope {

package/dist/src/im/feishu/config.d.ts

@@ -8,6 +8,31 @@ export interface FeishuAccessList {
     /** Feishu chat_ids the bot is permitted to listen in. */
     allowChats: string[];
 }
+/**
+ * Outbound text-reply rendering mode (RFC-020 §16). Controls how
+ * `adapter.send` handles a text/markdown payload that doesn't already
+ * carry an `imagePath` / `files[]` (those upload routes are unaffected).
+ *
+ *  - "plain" (DEFAULT): always send `msg_type:text`. Bot replies are
+ *    fully copy-pasteable in Feishu; long replies are chunked into
+ *    multiple text messages instead of being PNG-rendered. This is the
+ *    correct default for issue/code/CLI bot replies where users want
+ *    to grab the text. Vincent 2026-06-30 explicit ask: "issue 发文字".
+ *
+ *  - "card": short markdown (bold, list, link, inline code) goes via
+ *    schema 1.0 interactive card with `markdown` element — text stays
+ *    copy-friendly + gets bolds/bullets styled. Heading/table/long
+ *    fall back to plain text (no PNG). Suited to operators who want
+ *    light formatting without losing copy.
+ *
+ *  - "auto": preserve the pre-2026-06-30 behavior — markdown with
+ *    headings / tables / >2000 chars is rendered to PNG via headless
+ *    chromium (#329 path), short markdown goes to schema 1.0 card,
+ *    plain text goes to msg_type:text. Highest fidelity at the cost
+ *    of copy-paste. Opt-in for operators who genuinely need rendered
+ *    tables / heading hierarchy in chat.
+ */
+export type OutboundRenderMode = "plain" | "card" | "auto";
 export interface FeishuChannelConfig {
     appId: string;
     appSecret: string;
@@ -20,6 +45,12 @@ export interface FeishuChannelConfig {
     auditRaw: boolean;
     /** Per-task timeout in ms; default 5 min (RFC-020 §4.5). */
     taskTimeoutMs: number;
+    /**
+     * RFC-020 §16 outbound rendering mode for text replies. Default `"plain"`.
+     * See `OutboundRenderMode` for per-mode semantics. Channels that omit
+     * the field get `"plain"` — Vincent's "issue 发文字" default.
+     */
+    outboundRender: OutboundRenderMode;
     /**
      * Absolute path to the channel directory. The adapter writes downloaded
      * inbound media to `<channelDir>/media/` (M5c). Populated by the loader so

package/dist/src/im/feishu/hub-upload.d.ts

@@ -0,0 +1,88 @@
+/**
+ * RFC-020 §17 — feishu inbound bridge → hub `/api/upload` integration.
+ *
+ * Vincent 2026-06-30: cross-machine agents (e.g. TM门户运维@toodadev2)
+ * delegated by the feishu-local bot can't read inbound attachments
+ * because the only thing they get is a host-local path that doesn't
+ * exist on the receiver's filesystem. #351 already wired agent-node's
+ * receiver to prefer `file_id` and pull via `GET /api/files/<id>` when
+ * present. This module is the SENDER half: the feishu bridge uploads
+ * each downloaded inbound file to the hub via `POST /api/upload`,
+ * gets back a `file_id`, and propagates it alongside the local path.
+ *
+ * Failure mode (load-bearing): every failure path returns `null` and
+ * the caller falls back to path-only. The bridge MUST NOT crash because
+ * the hub is down / overloaded / refused a 12 MiB cap. Single-host
+ * `agent-node` Read still works on the local path; only cross-host
+ * delegation degrades, no regression vs the pre-fix baseline.
+ *
+ * Concurrency cap: a single feishu message can carry many images; bursts
+ * to /api/upload would hammer the hub rate limit (60/hour per token).
+ * `uploadFilesToHubConcurrent` caps in-flight requests at `concurrency`
+ * (default 4) so a 20-image message takes 5 sequential rounds instead
+ * of 20 simultaneous open sockets + a likely rate-limit denial.
+ */
+/**
+ * Hub upload limit, mirrors `server/src/uploads.ts:MAX_UPLOAD_BYTES`.
+ * Anything bigger is skipped at the bridge — the hub would 413 anyway.
+ */
+export declare const HUB_UPLOAD_LIMIT_BYTES: number;
+/** Default in-flight cap for `uploadFilesToHubConcurrent`. */
+export declare const DEFAULT_UPLOAD_CONCURRENCY = 4;
+/**
+ * One file uploaded to the hub. `mime` and `size` are from the local
+ * filesystem read; `file_id` and `path` come from the hub's response.
+ *
+ * `file_id` is the canonical cross-machine handle — receiving agent
+ * resolves to bytes via `GET /api/files/<file_id>`. `path` is the
+ * hub-machine-local absolute path the hub stored to; on the sender
+ * side it's purely informational (we already have the source file).
+ */
+export interface HubUploadResult {
+    file_id: string;
+    path?: string;
+    mime?: string;
+    size?: number;
+    name?: string;
+}
+export interface HubUploadOpts {
+    /** Hub base URL, no trailing slash. Defaults to env. */
+    hubUrl: string;
+    /** Bearer token (ntok_ / utok_ / atok_). Defaults to env. */
+    authToken: string;
+    /** Optional MIME hint; sniffed by filename ext otherwise. */
+    mime?: string;
+    /** Optional override filename (defaults to basename(path)). */
+    name?: string;
+    /** Injectable for tests. Defaults to global fetch. */
+    fetch?: typeof fetch;
+}
+/**
+ * Upload one local file to `${hubUrl}/api/upload`. Returns the file
+ * descriptor on success, or `null` on any failure (caller falls back
+ * to path-only).
+ *
+ *  - File must exist + be ≤ 12 MiB. Larger → skipped silently with
+ *    a stderr warn; caller gets `null` and ships path-only.
+ *  - Auth via `Authorization: Bearer <token>`.
+ *  - `Content-Length` header is set by `fetch` when given a Blob body;
+ *    the hub validates it before consuming bytes.
+ *  - Multipart body with a single `file` field. The hub server
+ *    reads `form.get("file")` and stores under a new file_id.
+ *  - Any network error / non-2xx / malformed JSON response → null.
+ */
+export declare function uploadToHub(filePath: string, opts: HubUploadOpts): Promise<HubUploadResult | null>;
+/**
+ * Upload many files to the hub with a bounded concurrency window.
+ * Returns one result per input path, preserving order. A failed
+ * upload appears as `null` at that slot — caller composes path-only
+ * descriptors for those.
+ *
+ * Why this matters: one feishu post can carry an arbitrary number of
+ * images. Naive `Promise.all(paths.map(uploadToHub))` would open N
+ * simultaneous HTTPS sockets to the hub AND blow past the 60/hour
+ * per-token rate limit on a single message with >60 images. A
+ * concurrency cap of 4 means N/4 sequential rounds, predictable
+ * load, no head-of-line blocking on the agent's reply.
+ */
+export declare function uploadFilesToHubConcurrent(filePaths: string[], opts: HubUploadOpts, concurrency?: number): Promise<(HubUploadResult | null)[]>;

package/dist/src/im/feishu/markdown-image-renderer.d.ts

@@ -0,0 +1,61 @@
+/**
+ * RFC-020 §14 — markdown → image rendering for Feishu replies.
+ *
+ * Vincent 2026-06-29 path: Feishu's `markdown` card element doesn't
+ * render ATX headings or GFM tables (preview.7 caught only bold / list
+ * / link). Rather than partially support a moving subset of card
+ * elements, we render structured markdown to a PNG via headless
+ * chromium and send it through Feishu's image API (`im:resource:upload`
+ * scope). Pixel-perfect fidelity, zero schema fragility, text-not-
+ * copyable accepted as the tradeoff for "actually renders".
+ *
+ * Hybrid route (decided in adapter.send):
+ *   - plain text (no markdown markers)        → msg_type:"text"
+ *   - markdown WITHOUT heading / table / long → msg_type:"interactive" (schema 1.0 card with `markdown` element — keeps copy/paste for short bold/list/link replies; preview.7 path)
+ *   - markdown WITH heading / table / long    → THIS PATH (msg_type:"image" with rendered PNG)
+ *
+ * Renderer choice: `puppeteer-core` (no bundled chromium) + system
+ * chromium (apt install in Docker). Rationale:
+ *  - Pure-JS canvas-layout libraries (node-canvas, @napi-rs/canvas)
+ *    cost 4-6h of manual paragraph wrapping + table cell measurement
+ *    + Chinese width metrics; chromium does this natively.
+ *  - puppeteer-core (5MB) + system chromium (~100MB) is smaller than
+ *    full puppeteer (170MB) which bundles its own chromium.
+ *  - Headless screenshot ~500ms after warmup. Bot's heavy turn is 20-
+ *    70s; rendering cost is in the noise.
+ *
+ * Chromium reuse: we keep a single browser instance hot across
+ * renderings to avoid the ~2-3s cold-start per call. Auto-close on
+ * idle is a follow-up — agent-node worker lifetime is bounded.
+ */
+import { Buffer } from "node:buffer";
+/**
+ * Close the shared browser. Called from adapter.stop() during graceful
+ * worker shutdown. Subsequent render calls re-launch.
+ */
+export declare function closeBrowser(): Promise<void>;
+/**
+ * Render markdown text to a PNG buffer.
+ *
+ * Width is fixed at 800px (IM-friendly); height auto-fits content via
+ * `fullPage:true`. Returns the raw PNG bytes — caller hands them to
+ * `lark.im.image.create({image: Readable.from(buffer)})`.
+ *
+ * Throws on chromium launch failure or page navigation failure.
+ * Caller is responsible for fallback (e.g., send the raw text as a
+ * code block in the schema 1.0 card path).
+ */
+export declare function renderMarkdownToPng(text: string): Promise<Buffer>;
+/**
+ * Decide whether `renderMarkdownToPng` should be invoked for this reply
+ * text, vs. falling back to msg_type:"text" / msg_type:"interactive"
+ * (schema 1.0 card). Locked by 通信龙 3f70044c — trigger image when:
+ *   - text contains a markdown table (Feishu card can't render)
+ *   - text contains an ATX heading (Feishu card can't render)
+ *   - text length > 2000 chars (image is better than scrollable text wall)
+ *
+ * Returns false for short prose, single-line plain text, and short
+ * markdown lists / bold / link / inline-code which DO render fine in
+ * the schema 1.0 `markdown` card element.
+ */
+export declare function shouldRenderAsImage(text: string): boolean;

package/dist/src/im/feishu/outbound-marker.d.ts

@@ -0,0 +1,140 @@
+/**
+ * RFC-020 §15 — agent→bridge outbound file protocol.
+ *
+ * 2026-06-29 Vincent UAT: agent generated a PDF via reportlab + wrote it
+ * to `/work/feishu-attachments/<conv>/x.pdf`, then in text asked Vincent
+ * "I'm not sure if the system will auto-attach this — try another way?"
+ * The bridge has `adapter.send({files})` since #329, but no protocol
+ * told the agent how to signal "dispatch this file to the user".
+ *
+ * Convention: in its final reply, the agent emits one
+ *
+ *     [[send-file:/abs/path]]
+ *
+ * marker per file (one per line, end of reply). The bridge:
+ *
+ *   1. extracts every `[[send-file:...]]` token,
+ *   2. strips them from the user-visible text,
+ *   3. validates each path against an allowed-outbound-root whitelist
+ *      (`/work/feishu-attachments/<conn>/<chat>/` — same per-conversation
+ *      directory the LLM has Write access to under Layer B),
+ *   4. checks the file exists, is non-empty, and ≤ 30 MB (Feishu file_v1
+ *      upper bound),
+ *   5. magic-byte sniffs to choose `image_key` vs `file_key` upload route,
+ *   6. dispatches each file via `adapter.send({files:[...]})`,
+ *   7. emits a friendly fallback if validation fails — never the raw error.
+ *
+ * Pure module — no I/O, no IM SDK calls. The parser returns the cleaned
+ * text + a structured list of file requests; bridge.ts is responsible
+ * for filesystem checks and dispatching.
+ */
+/**
+ * One outbound-file request parsed from an agent reply.
+ *
+ *  - `raw`: the bytes between `[[send-file:` and `]]`, before any
+ *    normalization. Kept for stderr forensic.
+ *  - `normalized`: lexical-normalized absolute path (quote-strip, `..`
+ *    collapse, `//` collapse, `./` resolution against cwd). The
+ *    `validatedAbsolute` field is set later by the bridge after the
+ *    realpath / whitelist / exists check.
+ */
+export interface OutboundFileRequest {
+    raw: string;
+    normalized: string;
+}
+export interface MarkerParseResult {
+    /** Reply text with all `[[send-file:...]]` markers removed + adjacent
+     *  whitespace collapsed. May be empty (file-only reply). */
+    cleanedText: string;
+    /** Files in source order. Caller-side validation happens after. */
+    files: OutboundFileRequest[];
+}
+/**
+ * Lexically normalize a path token from the marker. NOT a full
+ * symlink/realpath resolver — bridge does that after this returns.
+ *
+ *  - Trim leading / trailing whitespace.
+ *  - Strip one layer of matching quotes (`"/x"` / `'/x'` → `/x`).
+ *  - `.` and `..` segments collapse via `path.posix.normalize`.
+ *  - Repeated `/` collapse.
+ *
+ * Returns an absolute path or the empty string if the input cannot be
+ * interpreted as an absolute path token (caller drops empties).
+ */
+export declare function normalizeMarkerPath(raw: string): string;
+/**
+ * Parse an agent reply into cleaned text + outbound-file requests.
+ *
+ * Empty / null input returns `{cleanedText: "", files: []}` so callers
+ * can safely pipe through without defensive checks.
+ *
+ * Marker-only reply (no surrounding text) returns `cleanedText: ""` —
+ * caller should NOT send an empty text message in that case; they only
+ * dispatch the files.
+ *
+ * Multiple markers on one reply are all captured. Adjacent whitespace
+ * around stripped markers is collapsed (no double blank lines).
+ */
+export declare function parseOutboundMarkers(reply: string | null | undefined): MarkerParseResult;
+export { OUTBOUND_ROOT, feishuConvKey, feishuOutboundDir } from "./outbound-paths.js";
+/**
+ * Validate a normalized absolute path against the per-conversation
+ * whitelist + size + existence checks. Returns null on success or a
+ * Chinese user-friendly reason on failure (the same string can be
+ * surfaced as a fallback text reply when ALL files fail validation).
+ *
+ * Filesystem-touching — bridge calls this AFTER `parseOutboundMarkers`.
+ *
+ * Two API shapes accepted (overload):
+ *
+ *   1. **Preferred**: caller passes `expectedDir` — the precomputed
+ *      `/work/feishu-attachments/<connectionName>/<convKey>/` value
+ *      from `feishuOutboundDir`. This guarantees what the agent was
+ *      TOLD to use (via cli.ts prompt injection) matches what we
+ *      ACCEPT here — no second algorithm.
+ *
+ *   2. **Legacy**: caller passes `connectionName` + `convKey`. We
+ *      compute the prefix here via the same helper. Kept for the
+ *      single-arg unit-test ergonomics + backwards-compat (the old
+ *      bridge wire-up shape).
+ *
+ * Params:
+ *   - p: normalized absolute path candidate
+ *   - expectedDir: precomputed whitelist directory (trailing `/`)
+ *     OR
+ *   - convKey + connectionName: legacy two-piece form
+ *   - statFn: optional override for tests (defaults to fs.statSync)
+ *   - realpathFn: optional override for tests (defaults to fs.realpathSync)
+ *
+ * The whitelist check uses literal `.startsWith(expectedDir)` — the
+ * trailing slash on `expectedDir` ensures `oc_abc/` doesn't accept
+ * paths under `oc_abc_evil/`.
+ */
+export interface ValidateOpts {
+    p: string;
+    /** Precomputed prefix (with trailing `/`). Preferred over convKey+connectionName. */
+    expectedDir?: string;
+    convKey?: string;
+    connectionName?: string;
+    statFn?: (p: string) => {
+        size: number;
+    };
+    realpathFn?: (p: string) => string;
+}
+export declare function validateOutboundPath(opts: ValidateOpts): string | null;
+/**
+ * Magic-byte sniffer — picks `image` vs `file` upload route. Reads the
+ * first 16 bytes only; safe to call before commitment. Returns:
+ *
+ *   - "image" when the bytes are a PNG / JPG / GIF / WebP / BMP signature
+ *     (Feishu image_v1 supports these natively, with chat inline render).
+ *   - "file" otherwise (PDF, TXT, audio, video, archive, …).
+ *
+ * Caller supplies a Buffer (bridge reads via fs.openSync + readSync).
+ */
+export declare function sniffFileKind(buf: Buffer): "image" | "file";
+/**
+ * User-facing fallback message when ALL marker validations fail and the
+ * stripped text is empty (would leave the user with no reply at all).
+ */
+export declare const ALL_FILES_FAILED_FALLBACK = "[\u6587\u4EF6\u9644\u4EF6\u53D1\u9001\u5931\u8D25] \u6211\u51C6\u5907\u597D\u4E86\u6587\u4EF6\u4F46\u5206\u53D1\u65F6\u51FA\u4E86\u95EE\u9898\u2014\u2014\u7A0D\u540E\u518D\u8BD5\u6216\u6362\u79CD\u65B9\u5F0F\u3002";

package/dist/src/im/feishu/outbound-paths.d.ts

@@ -0,0 +1,50 @@
+/**
+ * RFC-020 §15.1 — feishu outbound/attachment path helpers (SHARED).
+ *
+ * Single source of truth for `/work/feishu-attachments/<conn>/<convKey>/`
+ * naming. Used by:
+ *
+ *   - `adapter.ts` inbound `downloadImage` (subdir for received images),
+ *   - `bridge.ts` outbound marker whitelist (where the agent may write),
+ *   - `worker.ts` outbound envelope (the concrete path injected into the
+ *     agent's prompt, so what we tell the agent matches what we accept).
+ *
+ * 2026-06-29 Vincent UAT: prior to this module, the inbound downloader
+ * used `conversationId.replace(/[^a-zA-Z0-9_-]/g, "_")` and the outbound
+ * bridge whitelist used `sender.id` for DMs / `chatId` for groups. The
+ * two algorithms diverged — agent learned the inbound oc_<chat>/ layout
+ * from incoming attachments, then wrote outbound files to the same
+ * oc_<chat>/ subdir, but the bridge required ou_<userid>/. Every PDF
+ * generated by the bot was rejected. This module unifies on
+ * `conversationId` (the open_chat_id assigned by Feishu — present for
+ * DMs and groups equally).
+ */
+/**
+ * Sanitize a raw Feishu conversation id (`oc_<hex>` / occasionally
+ * `om_<id>` for DMs) into a filesystem-safe segment. Identical to the
+ * adapter.ts inbound download path policy — DO NOT CHANGE without also
+ * migrating any on-disk attachments under the old key.
+ *
+ * The regex strips anything outside `[A-Za-z0-9_-]`, replacing with `_`.
+ * Falsy / non-string input returns the empty string; caller is
+ * responsible for substituting a fallback (the empty key would resolve
+ * to `/work/feishu-attachments/<conn>//` which the path-prefix
+ * whitelist rejects cleanly).
+ */
+export declare function feishuConvKey(rawId: string | undefined | null): string;
+/**
+ * Compute the canonical per-conversation directory for outbound file
+ * dispatch + inbound attachment downloads. Trailing slash included so
+ * `.startsWith(...)` whitelist checks are unambiguous about the
+ * conversation boundary (no `oc_abc` matching `oc_abc_x`).
+ *
+ * Example:
+ *   feishuOutboundDir("feishu-local", "oc_9a7eedbba275a87999f7ee2cfb10f4cb")
+ *   → "/work/feishu-attachments/feishu-local/oc_9a7eedbba275a87999f7ee2cfb10f4cb/"
+ */
+export declare function feishuOutboundDir(connectionName: string, rawConvId: string | undefined | null): string;
+/**
+ * The fixed prefix root used as a sanity check by the marker validator.
+ * Useful for tests + for `validateOutboundPath` defense-in-depth.
+ */
+export declare const OUTBOUND_ROOT = "/work/feishu-attachments";

package/dist/src/im/feishu/outbound-route.d.ts

@@ -0,0 +1,62 @@
+/**
+ * RFC-020 §16.1 — feishu outbound route decision (pure helper).
+ *
+ * Single source of truth for the `adapter.send` decision tree that
+ * picks among text / interactive card / image (rendered PNG) / file /
+ * imagePath outputs. Extracted into a pure module so the production
+ * call site AND the unit tests can bind the same function — previously
+ * the test mirrored the decision tree in a sibling `pickRoute` helper,
+ * which would drift silently if the production tree changed.
+ *
+ * Inputs are the minimal data the decision needs:
+ *
+ *   - `text` / `imagePath` / `files` — payload from `NormalizedIMMessage`
+ *   - `forceTextOnly` — caption-mode hint (RFC-020 §15.2)
+ *   - `mode` — channel-config `outboundRender` (`"plain"` / `"card"` /
+ *     `"auto"`, RFC-020 §16)
+ *
+ * Outputs the chosen `route` plus a short `reason` string for log /
+ * debug. The CALLER (adapter.send) actually performs the upload /
+ * render side-effects keyed on the route — this function does no I/O.
+ *
+ * Behavior contract (mirrors adapter.send line-for-line, locked by
+ * `feishu-outbound-render-mode.test.ts`):
+ *
+ *   1. `imagePath` set → `image_upload`
+ *   2. `files[0].path` set → `file_upload`
+ *   3. `forceTextOnly` true → `text`
+ *   4. mode "plain" → `text` (always)
+ *   5. mode "card" → `card_short_md` iff `looksLikeMarkdown(text)` AND
+ *      NOT `shouldRenderAsImage(text)`; else `text`
+ *   6. mode "auto" → `image_render` iff `shouldRenderAsImage(text)`;
+ *      else `card_short_md` iff `looksLikeMarkdown(text)`; else `text`
+ *   7. unknown mode (defensive default-default) → `text`
+ *
+ * The production switch in adapter.send may add the actual upload /
+ * render / lark API calls keyed on the route, but the route itself
+ * is decided HERE. To change the decision, change this file.
+ */
+export type OutboundRoute = "image_upload" | "file_upload" | "text" | "card_short_md" | "image_render";
+export interface RouteInput {
+    text?: string;
+    imagePath?: string;
+    files?: {
+        name: string;
+        path?: string;
+    }[];
+    forceTextOnly?: boolean;
+    /** `outboundRender` from the channel config. Defaults to "plain" when
+     *  absent so a caller that doesn't read the config still gets the
+     *  "Vincent default" behavior. */
+    mode?: "plain" | "card" | "auto";
+}
+export interface RouteDecision {
+    route: OutboundRoute;
+    reason: string;
+}
+/**
+ * Decide the outbound route for a `NormalizedIMMessage` (or a subset
+ * of its fields). Pure — no I/O, no SDK calls; safe to call from tests
+ * directly.
+ */
+export declare function resolveOutboundRoute(input: RouteInput): RouteDecision;

package/dist/src/im/feishu/worker-lifecycle.d.ts

@@ -0,0 +1,13 @@
+interface WorkerProcessBoundary {
+    stderr: {
+        write(message: string): unknown;
+    };
+    exit(code: number): unknown;
+}
+/**
+ * A terminal WS error means this worker no longer owns a live ingress path.
+ * Exit non-zero so the parent/supervisor cannot continue advertising it as
+ * healthy. Kept separate from worker.ts so the real exit contract is testable.
+ */
+export declare function exitFeishuWorker(error: Error, boundary?: WorkerProcessBoundary): void;
+export {};