IM tracer: work-group @Bot → PersonaBot Inbox → same-topic reply #12

Confirmed identity boundary — 2026-09-30

Cross-platform bindings are allowed; initially one account per platform per PersonaBot, and one platform Bot account bound to one local PersonaBot. This real work-group acceptance includes a Human-visible explicit binding and uses the existing canonical Inbox/Orchestrator authorities.

Feature Project and provider coordination

• Project: IM Identities & Messaging
• Native provider parent: IM identities and messaging: provider coordination #48
• Historical roadmap [Retired] Roadmap hub: M1–M7（PersonaBot → SoulSnapshot → Registry） #20 is retired.

Goal

交付 DeepSeekBot 的第一条真实 Feishu/Lark inbound tracer：Human 在一个已授权的工作群／话题中 @ 一个已绑定的 Bot；消息经 provider adapter、Messaging、Bot Inbox 与现有 Orchestrator 进入对应 PersonaBot，随后沿 trusted Reply Route 回到原 provider account / group / thread。

本票拥有 Human-facing end-to-end acceptance；#117 只拥有 outbound-first dsh-im adapter，#48 是 provider 系列的 coordination parent。Slack/Discord second-provider proof 要在本票获得 Human 反馈后另建 sibling tracer，不塞进本票。

Production-shaped path

verified Feishu/Lark work-group @mention
→ exclusive dsh-im external-consumer seam
→ #46 Messaging Ingress transaction
→ Source Event + Inbox Admission (Channel placement only for an explicitly configured Channel target)
→ #47 Wake/Delivery Policy
→ current Orchestrator Session
→ explicit reply command
→ Outbox Intent
→ trusted Reply Route / Provider Operation
→ Human receives the reply

必须使用真实 provider sandbox/account、DSH Credential reference、botharness.db authority、现有 V1 Session ownership/Orchestrator runtime，以及可重复的 integration evidence。dsh-im 被接管的 account 不得同时运行自己的 Session mapping / ask path；consumer 消失时 fail closed，不自动回退 standalone。

Acceptance criteria

• authenticated inbound 只产生一个 Source Event；duplicate/replay 不产生第二个 Attention 或重复回复。
• provider account、Actor、conversation/thread/reply identity 全部来自 authenticated adapter evidence。
• 群／话题、root/parent/reply 身份及被提及的 Bot 来自 authenticated adapter evidence；@其他 Bot 不能唤醒当前 PersonaBot。
• 收到普通群消息不等于必须回复；adapter 保留 mention/context 事实，Messaging / attention / Wake Policy 决定 admission 与执行。首片覆盖已授权工作群的 Human text @mention，普通消息上下文的扩展在该片反馈后推进。
• ordinary inbound 不 cancel 当前 model/tool step；Wake/Delivery 只在经验证的安全边界发生。
• reply destination 只来自 Source Event 的 trusted Reply Route；模型不能提供任意 provider target。
• Outbox Intent 先于外部调用；receipt/failure/unknown-outcome 可区分且不盲目重试。
• unauthorized sender、consumer disappearance、credential removal、archived PersonaBot 与 stale route 全部 fail closed。
• Host restart + provider redelivery 不产生重复 admission、attention 或 reply。
• Human 能在真实 Feishu/Lark 工作群及已有话题中 @bot，并收到对应 PersonaBot 在同一群／话题上的回复；不会串群、串话题或同时由 dsh-im standalone 再回复。
• secret 不进入 repo、Source Event、日志、RPC 或 Client state。

Blocked by

• Shared Bot Inbox/Wake baseline: delivered under Hub: Bot attention policy & turn harvest #362/Slice: split wake runners by Source class #363–Slice: Bot attention-policy tools, Human override, wake visibility #370; this tracer validates its actual external-source integration. Do not wait for every unrelated Bot Attention: causal aggregation, escalation and recovery acceptance #47 recovery residual.
• Research：Feishu/Lark Messaging provider contract（events / capabilities / identity） #78 — 本 tracer 实际使用的最小 Feishu/Lark 官方行为与 sandbox evidence。
• IM tracer: dsh-im outbound adapter and explicit Bot binding #117 — outbound-first dsh-im adapter、Binding/Grant/Outbox 与 provider lifecycle 基础。

#46 supplies the provider contracts exercised by #117. Existing explicit Session ownership/runtime are reused; exact gaps belong to this tracer, not a broad foundation completion gate.

Work-group policy clarification — 2026-10-01

Confirmed Group / optional Thread policy is specified in #48 ("Confirmed external Group / Thread policy"). New external groups default to direct-mention-only Inbox admission and @addressed replies. Human can enable full ordinary-message admission and configure the existing count/time digest harvest, immediate wake, mentions or silent policy; admission, wake and response remain independent. Unlike the internal Wake Policy's mentions preset, the external admission scope may exclude ordinary messages from the Bot Inbox entirely.

The Bot can explicitly follow/unfollow a verified Thread within its authorized group; posting a reply does not auto-follow. Group defaults and exact Thread overrides are durable Bot-owned policy with Human override. Thread capability is optional: Slack/Discord/Feishu/Lark adapt their actual provider hierarchy; QQ/WeChat providers without this capability retain group-only behavior. Do not manufacture Threads or platform-specific Orchestrator wake runners.

This issue still owns only the first bound-PersonaBot group/existing-Thread @mention tracer. Preserve authenticated Thread facts and policy seams, but do not add autonomous Thread following, all-group collection or a complete search/history layer to its completion claim. After #12 Human acceptance, choose the next runnable context-read / Thread-following slice under #48, with real Bot-identity capability evidence and screenshots/recording. #607 qualifies the current provider @mention path only; its QA goal remains paused.

Bridge target clarification — 2026-10-01

The generic target model is confirmed in #48 ("Confirmed Channel-targeted and Inbox-targeted Bridges"). This narrow bound-PersonaBot tracer may receive into the Bot Inbox without manufacturing a local Human DM or Group transcript. External platform, original conversation/Thread, sender and authenticated receiving identity must remain discoverable with the Source Event and trusted reply context. Source persistence and Bot access do not require local Channel placement; an external reply still returns through the Host-selected original route.

Keep #12's existing work-group/Thread @mention acceptance. Channel-targeted multi-Bot visibility, livestream transport, morning-report scheduling and a mandatory takeover/work-item model are not added to this issue. Outbound/provider echoes do not become self-attention merely to retain readable sent history. #624 remains paused for Human QA.

Out of scope

• Slack/Discord second-provider proof。
• 首片之外的完整群历史同步、多个 Bot 协作、rich card、attachment、edit/reaction 与 streaming reply breadth。
• 私聊作为后续兼容场景，不是首条验收或工作群能力的前置条件。
• TTS、Live2D 或其他 PersonaBot Output Event consumer。
• 把外部内容自动写入 Memory，或让 provider route 获得 Workspace authority。

References

• [Retired] Post-M4: Messaging / Bot Inbox / Orchestrator / Assignments #30、Messaging: external ingress, Provider contracts and Outbox #46、Bot Attention: causal aggregation, escalation and recovery acceptance #47、IM identities and messaging: provider coordination #48、Research：Feishu/Lark Messaging provider contract（events / capabilities / identity） #78、IM tracer: dsh-im outbound adapter and explicit Bot binding #117
• ADR-0026、ADR-0036～0039、ADR-0041、ADR-0045