Repository navigation
Slack tracer: verified pairing and native Allow once / Reject #1046
Description
Parent
What to build
A Slack actor initiates verified management pairing, receives explicit Web authorization and decides native Allow once/Reject through qualified Slack interactions with genuine result/status.
Acceptance criteria
- Qualify the required control reception/private delivery and Socket Mode interaction path; existing public event callbacks are not proof of DM/action support.
- Use stable verified workspace/account/actor identities, independent per-Bot capability and named destination, with explicit Web review.
- Implement the minimum real Block Kit send/action/update capability using the existing checked Provider boundary; acknowledge promptly without holding the intake queue.
- Resolve through the existing canonical broker, provide one real allow-once execution and rejection, and keep acceptance/result distinct.
- Refuse wrong actor/account, copied controls, revoked identity, Web/IM races, duplicate actions, expiry and restart replay.
- Verify concrete Slack app/interactivity permissions separately; no implicit ordinary-message subscription expansion or stale public-channel E2E claim.
- 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.
Activity