[Enhancement] Admin deep-dive (commerce/config): Bridge event subscriptions are tenant-wide booleans with only a forum-slug scope — no per-event channel routing

Area: Admin deep-dive (commerce/config) (audit p15b) · Surface: /admin/bridge (AdminBridgeController create/update) · Dimension: improve-existing · Severity: cosmetic

Slack/Teams power users in competitor integrations route different event classes to different channels (mods to #moderation, signups to #growth). We can approximate this only by creating N separate targets each with its own webhook URL, which is clumsy. Per-event routing within a workspace is the expected ergonomics.

Evidence

AdminBridgeController stores enabled_events as a flat JSON array and a single forum_scope per target (create lines 101-102, parseForumScope lines 339-348). A target either gets an event or it does not; there is no mapping of, say, moderation events to one channel and announcements to another beyond creating multiple whole targets.

Suggested fix. Allow an optional per-event channel override on a target, or document the multi-target pattern prominently; lower priority than adding Discord.

Filed by the automated tenant-app audit and adversarially evidence-verified. Status: verified. Open — not yet actioned.