openclaw-lark-multi-agent 1.4.2 → 1.4.3

package/README.md

@@ -10,7 +10,7 @@ This project is a bridge layer for OpenClaw. It does **not** implement an agent
 
 Lark/Feishu gives each bot its own app identity, but OpenClaw normally exposes one assistant identity per channel account. This bridge lets you create several Lark bots such as:
 
-- `GPT Bot` → `github-copilot/gpt-5.5`
+- `GPT Bot` → `phgeek-gw/gpt-5.6-sol`
 - `Gemini Bot` → `github-copilot/gemini-3.1-pro-preview`
 - `Claude Bot` → `github-copilot/claude-opus-4.7`
 
@@ -149,7 +149,7 @@ Edit `config.json`:
       "name": "GPT",
       "appId": "cli_xxx",
       "appSecret": "YOUR_LARK_APP_SECRET",
-      "model": "github-copilot/gpt-5.5"
+      "model": "phgeek-gw/gpt-5.6-sol"
     },
     {
       "name": "Gemini",

package/README.zh-CN.md

@@ -10,7 +10,7 @@
 
 Lark/飞书里每个机器人都有自己的 App 身份，但 OpenClaw 通常在一个 channel account 下暴露一个助手身份。这个桥接层可以让你创建多个飞书机器人，例如：
 
-- `GPT Bot` → `github-copilot/gpt-5.5`
+- `GPT Bot` → `phgeek-gw/gpt-5.6-sol`
 - `Gemini Bot` → `github-copilot/gemini-3.1-pro-preview`
 - `Claude Bot` → `github-copilot/claude-opus-4.7`
 
@@ -127,7 +127,7 @@ cp config.example.json config.json
       "name": "GPT",
       "appId": "cli_xxx",
       "appSecret": "YOUR_LARK_APP_SECRET",
-      "model": "github-copilot/gpt-5.5"
+      "model": "phgeek-gw/gpt-5.6-sol"
     },
     {
       "name": "Gemini",

package/config.example.json

@@ -14,7 +14,7 @@
       "name": "GPT",
       "appId": "cli_xxx2",
       "appSecret": "xxx2",
-      "model": "github-copilot/gpt-5.5"
+      "model": "phgeek-gw/gpt-5.6-sol"
     },
     {
       "name": "Gemini",

package/dist/cli.js

@@ -65,7 +65,7 @@ function sampleConfig() {
                 name: "GPT",
                 appId: "cli_xxx",
                 appSecret: "YOUR_LARK_APP_SECRET",
-                model: "github-copilot/gpt-5.5",
+                model: "phgeek-gw/gpt-5.6-sol",
             },
             {
                 name: "Gemini",

package/dist/feishu-bot.d.ts

@@ -35,6 +35,8 @@ export declare class FeishuBot {
     private sendQueue;
     /** Per-chat delayed runtime failure notifications, canceled if a real reply arrives. */
     private delayedFailureTimers;
+    /** Per-chat durable outbox retry timer. */
+    private deliveryRetryTimers;
     /** Last time a real assistant-visible reply was successfully handed to the delivery pipeline. */
     private lastRealDeliveryAt;
     /** Per-chat: whether we've already sent the high-context alert this cycle. */
@@ -118,6 +120,14 @@ export declare class FeishuBot {
     private cleanMentions;
     private stripLeadingCommandMentions;
     private buildMarkdownCard;
+    private deliveryOwnsVisiblePayload;
+    private completionSummary;
+    /** Final answer card used to replace the running live-status card in place. */
+    private buildFinalAnswerCard;
+    private patchFinalAnswerCard;
+    /** Best-effort cleanup when a final-card patch was too large/failed and the
+     * answer had to be delivered as a separate message. */
+    private patchLiveStatusDoneSummary;
     private formatUserVisibleError;
     private isBridgeControlReply;
     private isLegacyBridgeControlMessage;
@@ -126,16 +136,14 @@ export declare class FeishuBot {
      * Heuristic: does this reply look truncated / cut off mid-task? Used as the
      * SOLE auto-retry trigger — if true, we ask the session a one-line “done?” probe.
      *
-     * Signals (any one is enough):
-     *   1. Unbalanced code fence — almost certainly cut off mid code block.
-     *   2. Trailing clause-joining punctuation (comma/colon/semicolon/、) — a
-     *      sentence was left hanging.
-     *   3. A dangling connector / lead-in (“然后”, “接下来”, “let me”, “and”…).
-     *   4. Ends without ANY sentence-ending punctuation / closer (no terminal
-     *      punctuation, closing bracket/quote, code fence, or wrap-up emoji).
-     *      Per Stephen: a reply that ends with no punctuation at all is also
-     *      treated as likely unfinished. A false positive only costs one cheap,
-     *      invisible confirmation probe; the session itself is the real arbiter.
+     * Signals are intentionally HIGH PRECISION. A reply is suspicious only when:
+     *   1. Its Markdown/code structure is visibly unclosed; or
+     *   2. It ends on punctuation/words that grammatically demand continuation.
+     *
+     * Merely lacking a final punctuation mark is NOT enough. Short answers,
+     * headings, model lists, paths, hashes, commands, English labels, and normal
+     * chat prose routinely end without punctuation; treating all of them as
+     * truncated caused obvious false-positive confirmation probes.
      */
     private looksTruncated;
     /** Current context usage percent for a session (totalTokens / contextTokens),
@@ -178,6 +186,7 @@ export declare class FeishuBot {
     private deliverySourceId;
     private sendSystemDelivery;
     private enqueueAndDispatchDelivery;
+    private scheduleDeliveryRetry;
     private dispatchPendingDeliveries;
     private hasFreeModeBot;
     private mentionedBotNames;