[Improve] Link automation runs to their triggering event

[roomote-roomote]

​Opened on behalf of @mrubens. Follow up by mentioning @roomote-roomote, in the web UI, or in Slack.

What changed

• Add a source action beside recent automation runs when the original launch came from a Slack message or source-control issue.
• Preserve issue provenance explicitly on issue-fixer task payloads and derive history links from the original fresh run, so later resumes cannot replace the trigger.
• Keep scheduled runs and Slack report destinations unlinked rather than presenting output threads as triggering events.

Why this change was made

Automation history already linked to the task Roomote launched, but it did not help an operator answer why that run started. The original trigger is the shortest path back to the request, alert, or issue that needs context.

Impact

Admins can move directly from supported automation history entries to the Slack message or issue that caused the run while retaining the existing task link. URL handling is limited to HTTP(S), and unavailable provenance continues to render the existing history row without a source action.

Focused issue-fixer coverage, repository formatting, lint, fast type checks, knip, and pre-push gates pass. The new database-backed history regression is included but could not run in this sandbox because Docker and the test Postgres service were unavailable; browser proof was also unavailable because this run did not provide the delegated proof runtime.

[roomote-community]

1 issue outstanding. See task

• apps/web/src/components/settings/automations/AutomationsSettings.tsx:1373 The source action is rendered only through a debug panel that is hard-coded off, so it is unreachable.

_{Reviewed 85645d5}

[roomote-community]

The new source action is unreachable in production: renderDebugRunsSection always returns null because showAutomationDebugRuns is hard-coded to false (line 1622). As a result, neither this button nor any recent-run history is rendered, so operators cannot open the triggering event. Enable the panel (or move this action into a visible settings surface) before shipping.