[safe-output-health] 🏥 Safe Output Health Report — 2026-06-14

[github-actions[bot]]

Executive Summary

• Period: last 24h (runs 2026-06-13T21:38Z → 2026-06-14T05:46Z)
• Runs analyzed: 68 — copilot 40, claude 14, codex 5, antigravity 1, gemini 1, pi 1
• Run-level failures: 8 → 2 are safe-output JOB failures (in scope), 6 are agent-job failures (out of scope)
• Both in-scope failures are smoke-only (Smoke Claude, Smoke Copilot) — no production safe_outputs job failed
• Safe-output items emitted: 29 · Failed messages: 3 · Clusters: 1 recurrence + 1 new
• Streak: 🔴 broken after 2 clean days (06-12, 06-13); echoes the 06-11 break

Safe Output Job Statistics

Job conclusions confirmed per-run via the audit MCP tool. The 6 out-of-scope runs all had safe_outputs skipped (agent failed first) or emitted no items.

Run	Workflow	Agent	safe_outputs	In scope
§...196	Smoke Claude	✅	❌ fail	✅
§...799	Smoke Copilot	✅	❌ fail	✅
§...377	Code Simplifier	❌	skipped	❌
§...602	Daily Model Inventory Checker	❌	skipped	❌
§...197	Smoke Gemini	❌	skipped	❌
§...494	PR Sous Chef #801	❌	no items	❌
§...978	PR Sous Chef #800	❌	no items	❌
§...900	PR Sous Chef #799	❌	no items	❌

Failed messages: add_comment→discussion (Smoke Claude), add_labels + remove_labels (Smoke Copilot).

Error Clusters

Cluster 1 — RECURRENCE: add_labels/remove_labels hard-fail with no issue/PR context

• Occurrence 2 of target_star_add_labels_no_item_number_hardfail (first seen 06-11). 2 messages, 1 run.
• Where: Smoke Copilot §27481382799 (workflow_dispatch)
• Error: ✗ Message 14 (add_labels) failed: No issue/PR number available (+ remove_labels msg 15)
• Root cause: No resolvable issue/PR number in a workflow_dispatch context. add_labels/remove_labels hard-fail the job — yet in the same run comment_memory, create_pull_request_review_comment, and reply_to_pull_request_review_comment soft-skip (⏭) the identical condition. Reproduced on 2 separate days → strongest evidence yet of the soft-skip-vs-hard-fail inconsistency.

Cluster 2 — NEW: add_comment → discussion "Resource not accessible by integration"

• New pattern add_comment_discussion_resource_not_accessible_by_integration. 1 message, 1 run.
• Where: Smoke Claude §27480363196 (pull_request Fix AIC usage cache always empty in activation job #39130)
• Error: #335 not found as issue/PR, retrying as discussion... ##[error]Failed to add comment to discussion: ... Resource not accessible by integration
• Root cause: The safe_outputs job token grants Checks/Issues/PullRequests/SecurityEvents=write, Contents/Metadata=read — no Discussions scope. add_comment 404'd as issue/PR, fell through to the discussion path, and addDiscussionComment needs discussions: write. The 06-04 audit saw this same 404→discussion fallback succeed, so this is a fresh exposure of the missing scope. (resolve_pull_request_review_thread in the same run soft-skipped on the same permission family; the PR review #4492134465 submitted cleanly, no 422.)

Root Cause Analysis

• Handler-consistency (dominant theme): handlers disagree on missing trigger context / unavailable scope. Review-comment, reply, comment_memory, and resolve_pull_request_review_thread soft-skip (job stays green); add_labels, remove_labels, update_issue (06-11), and the discussion add_comment fallback hard-fail (job red).
• Permission: missing discussions: write on the smoke safe_outputs token (Cluster 2).
• Out of scope: 3× PR Sous Chef (Consolidate team membership validation to task job with workflow cancellation (#793) #799/Fix missing staged environment variable in create-discussion jobs #800/Refactor MCP server configuration into centralized provider and remove deprecated RenderMCPConfig function #801), Code Simplifier, Daily Model Inventory Checker, Smoke Gemini — agent-stage failures.

Recommendations & Work Items

No critical issues — both in-scope failures are smoke-only.

1. Soft-skip add_labels/remove_labels on missing context (Bug, Medium, Small effort).
   When no issue/PR number is resolvable, emit ⏭ with a message suggesting target: "*" + explicit number, instead of ##[error]. Add a unit test for the no-context branch. Ideally landed with the open LintMonster update_issue_target_triggering_default_hardfails_scheduled_run fix (same family).

   • Acceptance: no-context add_labels/remove_labels no longer fail the job; Smoke Copilot workflow_dispatch goes green.

2. Graceful discussion add_comment permission handling (Bug/Config, Low, Small effort).
   Either grant the safe_outputs job discussions: write (if discussion comments are intended), or treat a permission-scope failure on the best-effort discussion fallback as a soft-skip (like resolve_pull_request_review_thread); surface the missing scope in the error. Optionally point the smoke add_comment target (Welcome to Agentic Workflows! #335) at a resolvable issue/PR.

   • Acceptance: discussion-fallback permission error no longer fails the job (or scope granted); Smoke Claude goes green.

Historical Trend

Date	hard failures	Note
06-09 / 06-10	0 / 0	8th / 9th clean day
06-11	3	streak broken — target/context family (incl. LintMonster production)
06-12 / 06-13	0 / 0	clean recovery (x2)
06-14	2	broken again — both smoke-only

• Target/context-resolution family remains the dominant recurring theme; today reproduces the label no-context hard-fail (now 2 occurrences) + adds a discussion-permission variant. Unlike 06-11, zero production failures (LintMonster absent; its target:"*" fix still UNVALIDATED).
• Standing gap: review_path_unresolved_422 Path-variant fallback (pr_review_buffer.cjs:554) UNVALIDATED for the 17th consecutive audit.

Next Steps

• Land soft-skip unification for add_labels/remove_labels (+ LintMonster update_issue).
• Decide grant-scope vs. soft-skip for discussion add_comment.
• Keep watching the target/context family — it accounts for both recent streak-breaks.

References:

• §27480363196 — Smoke Claude (add_comment→discussion permission)
• §27481382799 — Smoke Copilot (add_labels/remove_labels no-context)

Generated by 🔒 Safe Output Health Monitor · 525.8 AIC · ⌖ 14.9 AIC · ⊞ 9.4K · ◷

• expires on Jun 14, 2026, 10:06 PM UTC-08:00

[github-actions[bot]]

This discussion was automatically closed because it expired on 2026-06-15T06:06:51.457Z.

Closed by Workflow