Discord feedback tracer: source reactions, typing and generic shared activity #1045

Parent

#1019

What to build

Discord shows source-correlated receipt/answer reactions, typing only for active reply preparation in that conversation, and generic shared PersonaBot activity across Lark and Discord.

Acceptance criteria

• Reuse the canonical receipt/answer correspondence established by Lark and qualify Discord’s own reaction operations.
• Typing starts only for relevant active reply preparation and stops for that work’s wait, failure, completion or stop; concurrent work retains its own indicators.
• Generic shared Working reflects canonical Bot activity but exposes no private message, participant, target or channel names.
• Honor platform timing/update limits and lifecycle cleanup on reconnect, unbind and disposal.
• No ✅ for silence, delegation or merely completing a model turn; provider acceptance does not mean recipient read.
• Verify actual Discord reactions/typing/presence with real cross-platform and parallel work, plus accurate Web configuration/status where applicable.
• Test through checked Provider and authenticated management/owning service boundaries; keep existing canonical persistence and no parallel content/decision authority.
• Retain real sanitized screenshots/step evidence and maintain the affected English/Chinese tutorial section; UI changes include matched baseline/changed light/dark evidence and no private secrets.
• Provide the exact-version runnable review path and focused behavioral coverage; pause for Human QA before expansion, without automatic merge/deployment.

Blocked by

• Lark feedback tracer: received and answered reactions from canonical facts #1040