Discord group tracer: named management destinations with qualified decision actors #1050

Parent

#1019

What to build

A Human selects a supported Discord management group/channel by name and uses the established questions/approvals with per-actor checks rather than membership-based authority.

Acceptance criteria

• Qualify the real conversation/target picker and this PersonaBot’s own authorized outgoing route; preserve DM usage.
• Demonstrate one native question and Allow once/Reject in a real chosen management conversation.
• An authorized actor can decide; another ordinary member, forwarded/copied control and revoked identity cannot.
• Keep management visibility/privacy explicit; no automatic command details or private links enter the public originating conversation.
• Existing supported rule controls continue to require explicit capability/confirmation rather than target membership.
• Verify stale/expired actions, account replacement and destination revocation through the provider and Web states.
• 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 tracer: management conversation destinations with per-actor question and approval checks #1034
• Discord tracer: native formal question answers and qualified clarification replies #1043