[safe-output-health] Safe Output Health Report - 2026-04-06

[github-actions[bot]]

Executive Summary

• Period: 2026-04-06 (last 24 hours)
• Runs Analyzed: 20 (recent batch from pre-downloaded logs)
• Workflows Active: 15 distinct workflows
• Runs with Safe Output Execution: 5 ✅
• Runs where Safe Outputs Skipped (due to agent failure): 5
• Safe Output Items Submitted: ~11
• Safe Output Items Executed Successfully: ~9
• Safe Output Hard Failures: 0 ✅
• Warnings: 1 (non-fatal PR review context)
• Error Clusters: 0

Overall system health: HEALTHY — fourth consecutive day with zero hard failures.

---

Safe Output Job Statistics

Job Type	Executions	Failures	Notes
create_discussion	3	0	Constraint Solving POTD, Auto-Triage, GitHub MCP
create_issue	2	0	PR Triage Agent, Smoke Copilot
add_labels	1	0	Auto-Triage Issues
set_issue_type	1	0	Smoke Copilot
submit_pull_request_review	1	0 ⚠️	Metadata set; finalization warning (no PR ctx)
create_pull_request_review_comment	0 (2 skipped)	0	Skipped — not in PR context

---

Observations

Non-Fatal Warning: submit_pull_request_review on Scheduled Run

• Run: §24032487186 — Smoke Copilot
• Warning: ##[warning]No review context set - cannot submit review
• Details: The Smoke Copilot workflow is schedule-triggered, not a PR event. The submit_pull_request_review message was processed successfully (message 3 ✓), but at finalization, there was no active PR context to submit the review body to. The system correctly counted this as Failed: 0 and emitted a warning rather than an error.
• Impact: None — review metadata deferred; all other outputs completed successfully (7/10 messages successful, 2 skipped, 1 custom job).
• Status: Expected behavior; consistent with prior observations.

---

Runs Where Safe Outputs Were Skipped (Infrastructure Failures)

These are not safe output failures. Safe outputs were correctly gated by the needs.detection.result == 'success' condition.

View Skipped Runs Detail

Run ID	Workflow	Reason
§24032836152	Smoke Create Cross-Repo PR	Agent failed — ##[error]Bad credentials on side-repo checkout
§24032644730	Smoke Update Cross-Repo PR	Agent failed — ##[error]Bad credentials on side-repo checkout
§24032222709	Smoke Gemini	Gemini CLI failed with exit code 41 (Failed to save project registry)
§24031918047	Smoke Claude	Agent job was skipped
§24032168801	Bot Detection	Agent job was skipped

Note on Cross-Repo Smoke Tests: Both Smoke Create Cross-Repo PR and Smoke Update Cross-Repo PR failed with Bad credentials when checking out githubnext/gh-aw-side-repo. This is an infrastructure/credentials issue outside the scope of safe output health, but worth monitoring as a recurring pattern.

Note on Smoke Gemini: Exit code 41 with a file system error (rename .tmp -> projects.json) suggests a transient file system condition in the Gemini CLI. Not a safe output concern.

---

Successful Safe Output Runs

View Successful Runs Detail

Smoke Copilot (§24032487186)

• 10 messages processed: 7 successful, 2 skipped (no PR context), 1 custom job
• Created discussion #24885, issue #24886
• Closed older discussions/issues with smoke-copilot key

Constraint Solving — Problem of the Day (§24032484822)

• create_discussion: success — closed 🧩 Constraint Solving POTD:Knapsack Problem — Packing & Cutting #24733, applied labels constraint-solving, problem-of-the-day

Auto-Triage Issues (§24032251288)

• add_labels: success
• create_discussion: success — closed [Auto-Triage] Auto-Triage Report — 2026-04-06 #24839, created new triage report

PR Triage Agent (§24031918046)

• create_issue: success — created #24880, closed [PR Triage Report] PR Triage Report - 2026-04-06 #24797

GitHub MCP Structural Analysis (§24031162917)

• create_discussion: success — created #24878

---

Historical Context

View 7-Day Trend

Date	Hard Failures	Warnings	Health
2026-03-31	1	—	Degraded
2026-04-01	1	—	Degraded
2026-04-02	0	1 (rate limit)	Healthy
2026-04-03	0	0	Healthy
2026-04-04	0	0	Healthy
2026-04-05	0	1 (add_comment limit)	Healthy
2026-04-06	0	1 (PR review ctx)	✅ Healthy

Trend: Four consecutive days of zero hard failures. Warnings are minor and expected (validation limits, context mismatches on schedule triggers).

Recurring patterns not seen today:

• push_to_pull_request_branch_files_outside_allowed_list (last: 2026-04-02)
• add_labels_no_issue_number (last: 2026-03-30)
• api_rate_limit_concurrent_burst (last: 2026-04-02)

---

Recommendations

No critical issues requiring immediate action.

Low Priority: submit_pull_request_review in Non-PR Context

The Smoke Copilot workflow tests submit_pull_request_review on a scheduled run, which produces a non-fatal warning at finalization. Consider either:

1. Adding a guard in the workflow to only call submit_pull_request_review when triggered by a PR event
2. Accepting the current behavior as-is (warning is informational, not actionable)

Monitor: Cross-Repo Smoke Test Credential Failures

Two cross-repo smoke tests (Smoke Create Cross-Repo PR, Smoke Update Cross-Repo PR) both showed Bad credentials on side-repo checkout. This has appeared before. If it becomes persistent, the side-repo token/credentials should be rotated or re-scoped.

---

Metrics

• Overall Safe Output Success Rate: 100% (0 hard failures / all executed items)
• Most Reliable Job Type: create_discussion, create_issue (100%)
• Warning-Level Issue: submit_pull_request_review finalization in non-PR context

References:

• §24032487186 — Smoke Copilot (PR review warning)
• §24032836152 — Smoke Create Cross-Repo PR (bad credentials)
• §24033036773 — This audit run

Generated by Safe Output Health Monitor · ● 406.5K · ◷

• expires on Apr 7, 2026, 1:21 PM UTC

[github-actions[bot]]

This discussion has been marked as outdated by Safe Output Health Monitor.

A newer discussion is available at Discussion #25096.