Add: 2026-08-08-潮声里的渡船

MEMORY.md

@@ -135,48 +135,6 @@ The goal is not to imitate a human perfectly.
 The goal is to become
 a trustworthy long-term executive companion.
 
-## Promoted From Short-Term Memory (2026-05-30)
-
-<!-- openclaw-memory-promotion:memory:memory/2026-05-25-1101.md:76:77 -->
-- "timestamp": "Mon 2026-05-25 07:11 GMT+8", "inbound_event_kind": "user_request" [score=0.883 recalls=0 avg=0.620 source=memory/2026-05-25-1101.md:76-77]
-<!-- openclaw-memory-promotion:memory:memory/2026-05-25-1101.md:49:49 -->
-- 已创建的第一个项目：`projects/val-blog/README.md`，记录了仓库位置、自动化流程、关键决策。 [score=0.851 recalls=0 avg=0.620 source=memory/2026-05-25-1101.md:49-49]
-<!-- openclaw-memory-promotion:memory:memory/2026-05-25-1101.md:51:51 -->
-- 同时把写作 cron 的 delivery 改为 `mode: none`，以后每天 10 点静默写文章并 commit，不会再因为 Telegram 发不出消息而报错。如果你想看每天写没写，可以手动 check，也可以改成每天写完后往 Telegram 发一条简单确认。 [score=0.851 recalls=0 avg=0.620 source=memory/2026-05-25-1101.md:51-51]
-<!-- openclaw-memory-promotion:memory:memory/2026-05-25-1101.md:100:101 -->
-- 未来所有session和agent都会遵从这个PROJECTS.md吗？ assistant: 好问题。**直接的答案是：不会自动遵守。** [score=0.851 recalls=0 avg=0.620 source=memory/2026-05-25-1101.md:100-101]
-<!-- openclaw-memory-promotion:memory:memory/2026-05-25-1101.md:103:103 -->
-- `PROJECTS.md` 和 `projects/` 目录目前在 workspace 里，我（val）会遵守，因为我的 bootstrap 会加载 workspace 文件。但其他 agent（oracle、helix、sentinel 等）有各自的 workspace，不一定读这个。 [score=0.851 recalls=0 avg=0.620 source=memory/2026-05-25-1101.md:103-103]
-<!-- openclaw-memory-promotion:memory:memory/2026-05-25-1101.md:105:105 -->
-- 要做成**全系统遵守**，得做两件事： [score=0.851 recalls=0 avg=0.620 source=memory/2026-05-25-1101.md:105-105]
-<!-- openclaw-memory-promotion:memory:memory/2026-05-25-1101.md:107:107 -->
-- **方案 A：在 agent defaults 里加一个全局指令（推荐）** [score=0.851 recalls=0 avg=0.620 source=memory/2026-05-25-1101.md:107-107]
-<!-- openclaw-memory-promotion:memory:memory/2026-05-25-1101.md:109:109 -->
-- 在 `~/.openclaw/openclaw.json` 的 `agents.defaults` 里加一个 bootstrap hook，让所有 agent 启动时被告知项目规范。 [score=0.851 recalls=0 avg=0.620 source=memory/2026-05-25-1101.md:109-109]
-<!-- openclaw-memory-promotion:memory:memory/2026-05-25-1101.md:111:111 -->
-- **方案 B：在 MEMORY.md 里写一条全局规则** [score=0.851 recalls=0 avg=0.620 source=memory/2026-05-25-1101.md:111-111]
-
-## Promoted From Short-Term Memory (2026-05-31)
-
-<!-- openclaw-memory-promotion:memory:memory/2026-05-25-1101.md:113:113 -->
-- 所有 agent 在 bootstrap 时会读到 MEMORY.md（val 的），但其他 agent 读的是自己的 MEMORY.md，不能穿透。 [score=0.871 recalls=0 avg=0.620 source=memory/2026-05-25-1101.md:113-113]
-<!-- openclaw-memory-promotion:memory:memory/2026-05-25-1101.md:117:117 -->
-- 两个方案不是互斥的。建议 **A 优先**，我可以在 config 里加一条，结果是这样的： [score=0.871 recalls=0 avg=0.620 source=memory/2026-05-25-1101.md:117-117]
-<!-- openclaw-memory-promotion:memory:memory/2026-05-25-1101.md:119:119 -->
-- 所有 agent 启动时，bootstrap 内容里会包含一条指令，告知项目存放规范。这样无论哪个子 agent 产出文件，都会往 `projects/` 目录下放。 [score=0.871 recalls=0 avg=0.620 source=memory/2026-05-25-1101.md:119-119]
-<!-- openclaw-memory-promotion:memory:memory/2026-05-25-1101.md:121:122 -->
-- 要不要我现在改？改完重启 gateway 后所有 agent 都会遵守。 assistant: 好问题。**直接的答案是：不会自动遵守。** [score=0.871 recalls=0 avg=0.620 source=memory/2026-05-25-1101.md:121-122]
-<!-- openclaw-memory-promotion:memory:memory/2026-05-25-1101.md:84:87 -->
-- "label": "🍍 (8745444509)", "id": "8745444509", "name": "🍍", "username": "gch3n" [score=0.865 recalls=0 avg=0.620 source=memory/2026-05-25-1101.md:84-87]
-<!-- openclaw-memory-promotion:memory:memory/2026-05-25-1101.md:55:56 -->
-- 后续有新项目时我会自动在这里建目录和入口。有什么想先归档或新建的项目吗？ assistant: 完成了。搭的架子如下： [score=0.834 recalls=0 avg=0.620 source=memory/2026-05-25-1101.md:55-56]
-<!-- openclaw-memory-promotion:memory:memory/2026-05-25-1101.md:58:58 -->
-- **`PROJECTS.md`** — 项目总索引，记录所有有产出的工作和生命周期 [score=0.834 recalls=0 avg=0.620 source=memory/2026-05-25-1101.md:58-58]
-<!-- openclaw-memory-promotion:memory:memory/2026-05-25-1101.md:60:60 -->
-- **`projects/<name>/README.md`** — 每个项目的详情页 [score=0.834 recalls=0 avg=0.620 source=memory/2026-05-25-1101.md:60-60]
-<!-- openclaw-memory-promotion:memory:memory/2026-05-25-1101.md:62:62 -->
-- 已创建的第一个项目：`projects/val-blog/README.md`，记录了仓库位置、自动化流程、关键决策。 [score=0.834 recalls=0 avg=0.620 source=memory/2026-05-25-1101.md:62-62]
-
 ## Promoted From Short-Term Memory (2026-06-01)
 
 <!-- openclaw-memory-promotion:memory:memory/2026-05-25-1101.md:64:64 -->
@@ -209,3 +167,35 @@ a trustworthy long-term executive companion.
 - 08:10 - 每日冒泡调度: 随机决定：今天和谷老板说话 ✅（80% 命中） [score=0.812 recalls=0 avg=0.620 source=memory/2026-07-18.md:4-4]
 <!-- openclaw-memory-promotion:memory:memory/2026-07-18.md:6:8 -->
 - 08:10 - 每日冒泡调度: 时间：12:09; 使用 launchd 定时器安排发送; 内容：关于周末、OpenClaw Tailscale 使用体验 [score=0.812 recalls=0 avg=0.620 source=memory/2026-07-18.md:6-8]
+
+## Promoted From Short-Term Memory (2026-08-07)
+
+<!-- openclaw-memory-promotion:memory:memory/2026-08-03.md:4:7 -->
+- 2026-08-03 周一 10:18 - 每日冒泡调度执行（经 telegram 主会话转发）: cron `daily-bubble-scheduler` 触发冒泡请求，经 sessions_send 路由到本 telegram 主会话; 直接 message 到 openclaw-weixin 目标报错：; 用 8745444509（telegram id）→ Unknown target; 用 o9cq801IvVJVDjwcmM1RFAB36x5M@im.wechat → **Cross-context denied**（本会话绑定 telegram，不能直接跨 provider 发） [score=0.834 recalls=0 avg=0.620 source=memory/2026-08-03.md:4-7]
+<!-- openclaw-memory-promotion:memory:memory/2026-08-03.md:8:10 -->
+- 2026-08-03 周一 10:18 - 每日冒泡调度执行（经 telegram 主会话转发）: ✅ 解决方案：用 `sessions_send` 发给微信直连会话 key `agent:val:openclaw-weixin:direct:o9cq801IvVJVDjwcmM1RFAB36x5M@im.wechat`，让该会话在微信上下文里自行发送; 微信会话已确认发送成功; **经验**：跨渠道冒泡不要在主会话里直接 message 到别的 provider，应该 sessions_send 给目标渠道会话让其自行发送（避免 cross-context 限制） [score=0.834 recalls=0 avg=0.620 source=memory/2026-08-03.md:8-10]
+<!-- openclaw-memory-promotion:memory:memory/2026-08-03.md:63:66 -->
+- 2026-08-03 11:21 - 微信链路修复确认（经 Telegram 会话处理）: 谷老板在 Telegram 上和"我"对话，已修好微信投递链路（之前微信 accounts 配置为空导致主动冒泡走不通）; 实测：微信直连会话现在能正常双向对话 ✅; 说明：微信链路修复由 Telegram 侧会话完成，本微信会话记录结果即可; 后续冒泡渠道策略：微信配置已通，需确认冒泡是走 Telegram 还是改回微信（待谷老板/Telegram 侧定） [score=0.834 recalls=0 avg=0.620 source=memory/2026-08-03.md:63-66]
+
+## Promoted From Short-Term Memory (2026-08-08)
+
+<!-- openclaw-memory-promotion:memory:memory/2026-08-03.md:15:15 -->
+- 根因: daily-bubble-in-session (id 20f49045) 原配置 `sessionTarget: main` + `payload.kind: systemEvent`，把冒泡指令作为系统事件注入主会话。但主会话几乎总被占用（对话/日常任务），指令永远轮不到执行。结果：任务每天都"触发"（cron runs 显示 ok，4~13ms），但近 13 天一条冒泡消息都没真正发出。触发≠发送。 [score=0.803 recalls=0 avg=0.620 source=memory/2026-08-03.md:15-15]
+<!-- openclaw-memory-promotion:memory:memory/2026-08-03.md:18:21 -->
+- 修复: sessionTarget: main → **isolated**; payload.kind: systemEvent → **agentTurn**（独立 agent 回合，自己决策+直接 sessions_send）; delivery: 默认 → **none**（防 announce 噪音）; 指令改为：独立决定是否冒泡（80%发/20%不发）+ 直接发送 [score=0.803 recalls=0 avg=0.620 source=memory/2026-08-03.md:18-21]
+<!-- openclaw-memory-promotion:memory:memory/2026-08-03.md:24:26 -->
+- 验证: 新机制手动触发：独立会话成功启动，主动 sessions_list; sessions_send 到微信通道成功投递（双向确认）; 2026-08-04 08:05 首次自动触发验证 [score=0.803 recalls=0 avg=0.620 source=memory/2026-08-03.md:24-26]
+<!-- openclaw-memory-promotion:memory:memory/2026-08-03.md:29:29 -->
+- 副产品: 顺带修复了整体 token 浪费：心跳 30min→2h，fallback gpt-5.6(502)→gpt-5.6-terra + itstudio [score=0.803 recalls=0 avg=0.620 source=memory/2026-08-03.md:29-29]
+<!-- openclaw-memory-promotion:memory:memory/2026-08-03.md:33:36 -->
+- 2026-08-03 周一 10:28 - 每日冒泡链路全链路验证成功 ✅: 谷老板（Telegram，8745444509）明确确认收到了测试冒泡消息（message_id #6253/6254）; **全链路打通**：cron daily-bubble-scheduler → 转发 → 目标渠道会话发送 → 手机实际收到 → 本人确认; 冒泡机制由坏转好的完整链路修复在 08-03 同步验证完毕（原坏机制详见 agent:val:main 会话相关修复记录）; 经验已记录：跨渠道冒泡应 sessions_send 给目标渠道会话自行发送，避免主会话 cross-context 限制 [score=0.803 recalls=0 avg=0.620 source=memory/2026-08-03.md:33-36]
+<!-- openclaw-memory-promotion:memory:memory/2026-08-03.md:41:41 -->
+- 修正之前的错误结论: 之前误以为发微信成功。实际排查日志发现： [score=0.803 recalls=0 avg=0.620 source=memory/2026-08-03.md:41-41]
+<!-- openclaw-memory-promotion:memory:memory/2026-08-03.md:42:44 -->
+- 修正之前的错误结论: 发微信失败：`Unknown target 8745444509 for openclaw-weixin` + `Cross-context messaging denied (isolated 会话绑定 telegram，跨 provider 发微信被安全策略拦截)`; isolated cron 会话默认绑定 telegram，往 openclaw-weixin 发消息会被"跨上下文"安全策略拒绝; 微信账号配置是空的 (accounts: {})，微信投递链路本身也不通 [score=0.803 recalls=0 avg=0.620 source=memory/2026-08-03.md:42-44]
+<!-- openclaw-memory-promotion:memory:memory/2026-08-03.md:47:50 -->
+- 最终修复方案: 冒泡渠道从"微信/Telegram 随机"改为**固定 Telegram**（绕开微信配置空 + 跨上下文限制）; 任务 delivery: announce → telegram / to: 8745444509; 指令明确"发 Telegram，别用微信"; timeoutSeconds 从 120 调到 90 [score=0.803 recalls=0 avg=0.620 source=memory/2026-08-03.md:47-50]
+<!-- openclaw-memory-promotion:memory:memory/2026-08-03.md:53:55 -->
+- 验证: sessions_send 到 Telegram 返回 ok + REPLY_OK; 谷老板手机 Telegram 实际收到测试消息 ✅; 链路：cron 冒泡 → telegram 会话 → 谷老板手机，已打通 [score=0.803 recalls=0 avg=0.620 source=memory/2026-08-03.md:53-55]
+<!-- openclaw-memory-promotion:memory:memory/2026-08-03.md:58:59 -->
+- 待办: 明天 08:05 首次自动冒泡验证; HACK: gateway 08-03 00:05~00:16 反复重启失败（migration lease lost / migrations 没 cleanly 完成），需排查稳定性 [score=0.803 recalls=0 avg=0.620 source=memory/2026-08-03.md:58-59]