Skip to content

Discord tracer: verified DM pairing and native Allow once / Reject #1042

Open

Description

@DoodleBears

v1.3 release reconciliation — 2026-10-11

Target release: v1.3. Native dependencies are #1029 (fulfilled Lark approval baseline) and #1123 (current-product Discord binding/checked-contract qualification, still open). Refresh the exact Provider source/digest and real app discovery before the DM/interaction tracer; #1123's old-pin diagnosis is historical, not proof that the current pin still fails. Preserve this issue's native management-pairing scope; ordinary roles/groups are coordinated in #1372. No claim or native permission expansion is made here.


Parent

#1019

What to build

A Discord user uses verified DM pairing, receives explicit Web review and resolves native Allow once/Reject requests through Discord controls, with independently managed cross-platform identity association.

Acceptance criteria

  • Qualify the real DM-capable command/interaction path and provider-authenticated actor/account; do not assume guild-mention intake already supports this.
  • Reuse current-Bot authorization, Web review, route selection, canonical approval and exact call/result correspondence established by Lark.
  • Allow explicit association with a verified Lark actor but never copy permissions by nickname/avatar; revoke one account independently.
  • Use native buttons, prompt acknowledgement and private refusal where available; original request updates after decision/expiry.
  • Prove one real allow-once execution and one denial, Web/IM race, wrong actor/account, duplicate click and revoked/stale controls.
  • Do not widen ordinary-message intake or claim Discord private capabilities from platform documentation alone.
  • 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

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:fullstackEnd-to-end Host and Client implementationfeature:messagingMessaging module and external providersready-for-agentFully specified, ready for an AFK agentscope:tracerHuman-testable implementation slice

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions