The drift-comment.yaml workflow_run companion currently reports only the workflow-drift job. When a different gated job fails (for example the Unit Tests job, where action-pins consistency-guard failures land), the PR shows a red gate with no inline explanation and a maintainer must open the run logs. Extend the single existing companion (do not add a second workflow_run workflow, which would race and double-comment) to extract the failed job plus root-cause lines from the triggering run (annotations first, short log tails, a few jobs), backtick-fencing any fork-supplied log text, and add a special case that prints the exact internal/generate/action_pins.yaml line to change when the pin consistency guard fails. Keep the sticky self-clearing on a green run, guarded on head_sha so a stale completion cannot overwrite a newer green comment. Must work on external fork PRs.
The
drift-comment.yamlworkflow_run companion currently reports only the workflow-drift job. When a different gated job fails (for example the Unit Tests job, where action-pins consistency-guard failures land), the PR shows a red gate with no inline explanation and a maintainer must open the run logs. Extend the single existing companion (do not add a second workflow_run workflow, which would race and double-comment) to extract the failed job plus root-cause lines from the triggering run (annotations first, short log tails, a few jobs), backtick-fencing any fork-supplied log text, and add a special case that prints the exactinternal/generate/action_pins.yamlline to change when the pin consistency guard fails. Keep the sticky self-clearing on a green run, guarded on head_sha so a stale completion cannot overwrite a newer green comment. Must work on external fork PRs.