igneum-josh 09fcd76b6f CI red watcher: its own workflow_run workflow (ci-red.yml) so the copy on master watches every branch's run whatever ci.yml the branch carries ... GitHub runs a workflow_run workflow from the default branch only, so a feature branch no longer waits for a merge of master before its reds are posted. record() reads the FAILED run from RED_WATCH_* (id, attempt, workflow, branch, sha, event, url, actor, title, author: the workflow_run payload) and asks the jobs API for that run, not the watcher's own; the inline GITHUB_* shape stays for a branch with the old `red` job (one line per run id either way). The inline job leaves ci.yml. Self-test covers the workflow_run shape and the full line. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>		2026-10-07 14:15:11 +01:00
..
ci-red.yml	CI red watcher: its own workflow_run workflow (ci-red.yml) so the copy on master watches every branch's run whatever ci.yml the branch carries	2026-10-07 14:15:11 +01:00
ci.yml	CI red watcher: its own workflow_run workflow (ci-red.yml) so the copy on master watches every branch's run whatever ci.yml the branch carries	2026-10-07 14:15:11 +01:00
windows.yml	red watcher job: actions:read on its token, so the recorded line names the failed job and step (the first real red run, windows-ci at 21:19Z, got 403 from the jobs API and recorded no step)	2026-10-06 22:20:10 +01:00