cc-connect-next v0.3.0-beta.2

cc-connect-next v0.3.0-beta.2

中文

这是 v0.3.0 的第二个 Beta，集中修复 Beta.1 发布后发现的两项兼容性与交互问题：
动态 Agent/Platform option 的嵌套配置不再被误报为不支持，飞书反馈按钮也会在提交
完成后直接把原卡片更新成明确的最终状态。

Beta 渠道

• 这个版本会作为 GitHub Prerelease 和 npm beta 发布，不会替换 GitHub Latest
  或 npm latest；稳定渠道继续保持 v0.2.1。

• daemon 更新提醒、cc-connect-next check-update 和内置
  cc-connect-next update 只查询 Stable，因此不会向稳定用户推送这个 Beta，也
  不会自动执行 Beta-to-Beta 更新。

• 明确参与 Beta 时使用：

  npm install -g cc-connect-next@beta
  cc-connect-next --version

主要变化

• 动态 option 配置不再误报。 Codex 的
  [projects.agent.options.env]、Feishu/Lark 的 mention_map 与 peer_bots
  等由 adapter 声明并消费的动态表，会保留完整键值且不再把嵌套叶子加入
  UnknownConfigKeys。真正未知的顶层 option 仍会报告，类型校验也保持不变。
• 反馈按钮显示明确结果。 用户点击飞书反馈确认按钮后，Relay 完成时会精确
  更新被点击的原卡片：成功只显示“提交成功”，失败、批准缺失/过期或通道停用只
  显示“提交失败”。卡片路径不再另发结果消息，也不展示 Relay 返回的 Issue
  链接；文字命令确认同样不输出 Issue 链接。

兼容边界

• 迁移器继续按目标 adapter 能力 fail closed：目标 Agent 不消费 env，或目标
  Platform 不支持 mention_map / peer_bots 时，迁移仍会明确拒绝，不能把本次
  诊断修复理解为所有动态表都可以跨 adapter 迁移。
• 精确更新原反馈卡片依赖飞书 card action callback 提供原始 message_id。普通
  文字 /feedback confirm 仍然可用，但继续走文字结果路径。
• 发布 Beta 不会升级、覆盖或重启当前正在运行的 daemon；安装、配置变更和真实
  平台验证仍需单独执行。

English

This is the second v0.3.0 Beta. It focuses on two compatibility and interaction
issues found after Beta.1: nested keys in dynamic Agent/Platform options are no
longer misreported as unsupported, and Feishu feedback actions now update the
clicked card with an explicit terminal result.

Beta channel

• This release is a GitHub Prerelease and npm beta. It does not replace
  GitHub Latest or npm latest; the stable channel remains v0.2.1.

• Daemon update notices, cc-connect-next check-update, and the built-in
  cc-connect-next update query Stable releases only. Stable users are not
  prompted to install this Beta, and Beta-to-Beta updates are not automatic.

• Opt in explicitly with:

  npm install -g cc-connect-next@beta
  cc-connect-next --version

Highlights

• Dynamic option keys are no longer false positives. Adapter-declared and
  consumed tables such as Codex [projects.agent.options.env] and Feishu/Lark
  mention_map or peer_bots preserve their complete values without adding
  nested leaves to UnknownConfigKeys. Truly unknown top-level options and
  value-type validation remain intact.
• Feedback actions show an explicit result. After a user confirms a
  Feishu feedback card, Relay completion updates that exact clicked card.
  Success shows only 提交成功; failure, missing or expired approval, and a
  disabled channel show only 提交失败. The card path sends no separate result
  message and never displays the Relay's Issue URL; typed confirmation also
  omits the URL.

Compatibility boundaries

• Migration remains capability-aware and fail closed. A target Agent that does
  not consume env, or a target Platform that does not support mention_map
  or peer_bots, still rejects those values explicitly. This diagnostic fix
  does not make every dynamic table portable across adapters.
• Exact feedback-card replacement depends on the Feishu card action callback
  carrying the original message_id. Typed /feedback confirm remains
  available through the text-result path.
• Publishing this Beta does not install, replace, or restart a running daemon.
  Installation, configuration changes, and real-platform validation remain
  separate actions.