Discord tracer: explicit rule-saving controls with independent identity revocation #1044

Parent

#1019

What to build

An authorized Discord rule saver uses native controls to save the same explicitly scoped approval rules and sees creator-specific revocation consistently in Web and IM.

Acceptance criteria

• Reuse canonical exact/all-opaque rule semantics and true actor/authorization provenance; no platform-specific rule authority.
• Require rule capability and second confirmation, with separately disclosed broader scope.
• Demonstrate a real matching automatic decision, complete-input mismatch and unauthorized rule-saving refusal.
• Revoking the Discord authorization disables its rules and old controls; independently authorized Lark identity remains valid and re-pairing restores nothing silently.
• Duplicate/competing actions create one accepted rule and cannot widen native, Workspace or provider authority.
• Render outcomes and scope in the real Discord/Web UI and retain reusable tutorial screenshots.
• 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: explicitly saved approval rules and creator-authorization revocation #1033
• Discord tracer: verified DM pairing and native Allow once / Reject #1042