You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
approve_workflow_run and push_to_pull_request_branch correctly refuse to act when a PR touches protected files (go.mod, go.sum, .github/workflows/** lock files, etc. — policy parsed via preprocessProtectedFilesField in pkg/workflow/config_preprocessing.go:139), but the decline is currently surfaced as a hard job failure rather than a soft skip/neutral outcome. Per Safe Output Health Monitor #57850 (2026-09-02), this is now PR Sous Chef's dominant and most persistent unresolved issue: 11 total occurrences over 7+ days, with a single-day spike of 7 failed items across 2 runs / 3 PRs (#57721, #57669, #57747) on 2026-09-02 alone. This exact fix was already proposed as #56576 on 2026-08-28 but auto-expired NOT_PLANNED before anyone landed it.
Expected Impact
Removes the top recurring source of safe_outputs job failures (2 of 3 failures in today's audit, 66.7% of today's total) and stops polluting success-rate metrics / generating false-alarm "failure" issues for what is actually correct policy behavior.
Suggested Agent
General-purpose agent — locate the runtime code path where approve_workflow_run/push_to_pull_request_branch emit a hard failure on a protected-files policy decline (downstream of the config parsed in pkg/workflow/config_preprocessing.go and pkg/workflow/push_to_pull_request_branch.go) and change it to a soft skip/neutral job outcome instead.
Estimated Effort
Medium
Data Source
DeepReport analysis 2026-09-02 cycle, from Safe Output Health Monitor #57850. Re-files expired #56576 (proposed 2026-08-28, auto-closed unfixed).
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
api.anthropic.com
To allow these domains, add them to the network.allowed list in your workflow frontmatter:
Description
approve_workflow_runandpush_to_pull_request_branchcorrectly refuse to act when a PR touches protected files (go.mod,go.sum,.github/workflows/**lock files, etc. — policy parsed viapreprocessProtectedFilesFieldinpkg/workflow/config_preprocessing.go:139), but the decline is currently surfaced as a hard job failure rather than a soft skip/neutral outcome. Per Safe Output Health Monitor #57850 (2026-09-02), this is now PR Sous Chef's dominant and most persistent unresolved issue: 11 total occurrences over 7+ days, with a single-day spike of 7 failed items across 2 runs / 3 PRs (#57721, #57669, #57747) on 2026-09-02 alone. This exact fix was already proposed as #56576 on 2026-08-28 but auto-expiredNOT_PLANNEDbefore anyone landed it.Expected Impact
Removes the top recurring source of safe_outputs job failures (2 of 3 failures in today's audit, 66.7% of today's total) and stops polluting success-rate metrics / generating false-alarm "failure" issues for what is actually correct policy behavior.
Suggested Agent
General-purpose agent — locate the runtime code path where
approve_workflow_run/push_to_pull_request_branchemit a hard failure on a protected-files policy decline (downstream of the config parsed inpkg/workflow/config_preprocessing.goandpkg/workflow/push_to_pull_request_branch.go) and change it to a soft skip/neutral job outcome instead.Estimated Effort
Medium
Data Source
DeepReport analysis 2026-09-02 cycle, from Safe Output Health Monitor #57850. Re-files expired #56576 (proposed 2026-08-28, auto-closed unfixed).
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
api.anthropic.comTo allow these domains, add them to the
network.allowedlist in your workflow frontmatter:See Network Configuration for more information.