Built on #1191, which replays the plugin resource-event catalog reviewed in #1184 directly onto main. Junior core persists event tasks that execute a durable instruction whenever an enabled plugin publishes a matching normalized resource event. The Slack tools search the runtime plugin catalog and create, list, update, or delete tasks for the current channel or DM. One task may select multiple event types, and multiple tasks may match the same resource.

Plugins only own webhook verification, event normalization, and catalog registration. Core owns configured tasks and matching. Every match starts an independent top-level Slack job through the existing agent-dispatch path; its state-backed idempotency key combines the task with the provider event key so webhook retries do not execute the same task twice. SQL stores only configured tasks: presence means the task exists, and deletion removes the row. There is no active/deleted status, pause state, tombstone, or separate run-history system.

Event tasks use the creator's connected credentials by default when the stored work needs user-bound access. Anyone in the same Slack destination can manage the task, while only the original creator can enable creator credential use; another actor changing executable instructions or the trigger clears that delegation. GitHub issue guidance supports one issue or repository-wide issue activity and multiple selected issue states in one task.

A code TODO records the remaining circuit-breaker work for runaway event loops rather than imposing an arbitrary execution quota in this change.

Refs #1174