docs(plan): IM 反向桥接（飞书先行）提案

[DeliciousBuding]

状态: PROPOSAL（管理员已批立项，设计待批）

摘要

产出完整的 IM 反向桥接 SPEC，覆盖 9 个核心设计问题，分三阶段 PR 计划（Phase 1 数据模型+飞书后端+推送，Phase 2 审批卡回调，Phase 3 多渠道抽象 trait 化）。

核心输出

• docs/plan/proposal-im-bridge.md（926 行完整 SPEC）
• 追踪 issue: 观察池：外部会话导入 / Office 实时预览 / 系统托盘状态外显（管理员定档 2026-07-27） #1407

关键决策

1. 桥接器住 hub-server（非 edge/desktop），理由：云端常驻 + 有账号体系 + 审批经 hub 路由
2. 飞书单渠道先行
3. IM 侧限 allow_once/deny，allow_always 类高权限决策锁在自有端
4. IM 只是通知面，审批真相在 hub（IM 发送失败不阻塞 web/mobile 路径）
5. 与 Mobile 互补：IM=降级触达，Mobile=完整体验

审查要点

• 9 问的回答是否覆盖完整
• 数据模型设计是否合理（4 张新表）
• 事件过滤逻辑（fail-closed + debounce + 豁免清单）
• Phase 1 工作量评估与验收方式
• 安全红线清单是否完整

不 merge——设计待管理员审批。

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[coderabbitai]

Warning

Review limit reached

@DeliciousBuding, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 35 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 83fdb828-9bec-4d65-8c6d-3f17aaca94a5

📥 Commits

Reviewing files that changed from the base of the PR and between aab56cd and 220d8a9.

📒 Files selected for processing (1)

• docs/plan/proposal-im-bridge.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/spec-im-bridge

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[DeliciousBuding]

独立审查结论（fable，只读，不 merge）

Verdict: NEEDS_FIX — 方向对，与现有身份/飞书 SSOT 有硬冲突，不宜按现状批准。

信任边界

• 已对：IM 仅 allow_once/deny，allow_always 锁自有端；Hub 合同 allow|deny。
• 须补：决策词统一；高风险策略与 authorization-model（高风险回 Web/ID）二选一写死；open_id → TokenDance 绑定 → Hub user → owner 全链 fail-closed；approval 幂等。

安全阻断

1. Critical 身份：绑定真相在 TokenDanceID/oauth_bindings，禁止 hub 自建主绑定 + open_id 当主身份。
2. High 生产入口：HTTPS Webhook（验签/解密/幂等/3s）为主；WS 仅 dev。
3. High 密钥：encrypt_key/verification_token 与 app_secret 同级加密。
4. High 3s+幂等：先 ack 再异步 DecideTaskApproval。
5. High 租户：MVP 平台 bot + 用户绑定；per-user bot 后续。
6. Med：签名步骤对齐官方；卡片 payload 白名单。

批次修订

Phase 0 设计补丁 → Phase 1 推送 only（瘦身）→ Phase 2 审批闭环 → Phase 3 多通道。

其他

• 追踪 issue 误挂 观察池：外部会话导入 / Office 实时预览 / 系统托盘状态外显（管理员定档 2026-07-27） #1407（观察池）须改。
• Q9 空壳；路由对齐 /integrations/feishu/*。
• 与 Mobile 互补、不抢主线。

最低修复清单齐后再 APPROVE_AS_PROPOSAL。未 merge。

[DeliciousBuding]

Approved design (admin): IM 反向桥接 立项已批, design approved (飞书单渠道先行). Author marked 不 merge — closing; implementation via #1407.