dresberandClaude Sonnet 5
602ff49f7b
notifications.yml is invoked via workflow_call from the caller workflow, so inside this job gitea.event_name reports "workflow_call" rather than the top-level event (push/schedule/...) that actually started the run. Comparing that against the Actions API's per-run event field (which reports the real trigger) never matched, so previous_conclusion always stayed "unknown" and healed notifications never fired. Now the current run's real event is captured from the API response itself and used for the comparison, falling back to gitea.event_name only if the current run isn't found in the scanned history. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>