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

[github-actions[bot]]

Executive Summary

• Period: Last 24h (partial early-morning batch, runs 05:00Z–05:53Z)
• Runs Analyzed: 13 dirs (12 excl. this self-monitor)
• Workflows Active: 11 (Issue Monster, Smoke CI ×2, Step Name Alignment, Doc Noob Tester, Designer Drift Audit, Sergo, Copilot Deep Research, jsweep, PR Sous Chef, AI Moderator, Refactoring Cadence)
• Safe Output Jobs Executed / Hard Failures: 12 / 0 (production JOB streak intact)
• Failed Messages (actuation): 0
• Pre-buffer Intent Failures: 1 (jsweep create_pull_request)
• New Error Clusters: 1

Headline: No safe_outputs job failed, but a production create_pull_request was silently dropped at a layer this monitor rarely sees — the safeoutputs MCP-handler branch-pin step — with a git detected dubious ownership error from the out-of-container bridge process. jsweep's daily PR was never created; the agent self-healed via report_incomplete.

Safe Output Job Statistics

Job Type	Executions	Failures	Success
create_issue	3	0	100%
create_discussion	3	0	100%
add_labels	1	0	100%
hide_comment	1	0	100%
assign_to_agent	2	0	100%
add_comment	5	0	100%
upload_asset	4	0	100%
noop	6	0	100%
report_incomplete	1	0 (self-heal)	100%
create_pull_request	3 attempts	3 dropped pre-buffer	0%

Lower bound — partial early-morning batch; downstream JOB logs confirmed per-run via the audit MCP tool.

Error Cluster (NEW): create_pull_request_branch_pin_dubious_ownership_bridge_process

• Workflow: jsweep — JavaScript Unbloater (production, copilot/sonnet-4.6), run §27667495270
• Severity: Medium — production intent dropped, gracefully self-healed (no red run)
• Sample Error:

  Failed to pin branch 'jsweep/write-large-content-to-file' before bundle generation:
  ERR_SYSTEM: fatal: detected dubious ownership in repository at '/home/runner/work/gh-aw/gh-aw'
  

• Timeline: 3 create_pull_request attempts (05:31:57 / 05:32:07 / 05:32:35) all returned {result:error}; agent emitted report_incomplete 05:33:08; downstream safe_outputs job processed it → non-fatal ##[warning] → Successful 1 / Failed 0 (job = success).
• Root Cause: The bundle-transport branch-pinning step ("Bundle transport requires branch pinning to prevent patch/bundle desynchronization") runs git inside the safeoutputs bridge process, which executes outside the agent container as a different user/HOME than the checkout. git refuses the foreign-owned worktree with dubious ownership. The agent's in-container git config --global --add safe.directory (and '*') cannot reach the bridge's gitconfig. The handler errors before buffering the message, so it never reaches the downstream job — the PR intent is dropped except for the report_incomplete warning footer.
• Impact: jsweep's daily cleanup PR (commit d216f3c: JSDoc fix + 4 new tests) was not created. Work is committed locally on branch jsweep/write-large-content-to-file but otherwise invisible — report_incomplete only wrote a warning, it did not open a tracking issue.
• Regression: jsweep created PRs cleanly on 06-12, 06-13 ([jsweep] Clean update_handler_factory.cjs #39019), 06-16. The branch-pin/bundle-transport path is the new variable. First branch-pin failure on record.

In-scope despite a green job: the create_pull_request path failed at the MCP-handler/bridge layer; the job is green only because the agent fell back to report_incomplete. A write the system was asked to perform did not happen — exactly what this monitor exists to surface.

Root Cause Summary

• Infrastructure/Bridge (the only finding): ownership mismatch between the safeoutputs bridge process and the container checkout for git. Not fixable from agent-side config.
• API/Permission: none. AI Moderator hide_comment + add_labels (codex, issue_comment ctx) and all issue/discussion/comment/assign writes clean.
• Validation: none. No collection-time rejections, no malformed payloads.

Recommendations & Work Items

WI-1 (High, Bug Fix): Resolve branch-pin dubious-ownership in the bridge.
Invoke the pin git with -c safe.directory=/home/runner/work/gh-aw/gh-aw (or '*'), or point the bridge's GIT_CONFIG_GLOBAL/HOME at a gitconfig whitelisting the checkout, or run the pin with matching uid/ownership.
Acceptance: a jsweep-equivalent create_pull_request passes the branch-pin step on this runner topology; unit/integration test covers the bridge-vs-container ownership case. Effort: Small–Medium. Affects any PR-emitting workflow hitting the branch-pin step from the out-of-container bridge.

WI-2 (Medium, Enhancement): Surface dropped intents from report_incomplete.
When create_report_incomplete_issue is configured (jsweep does), an incomplete signal should open a tracking issue, not just a run-summary footer — today the dropped daily PR is invisible. Effort: Small.

WI-3 (Low): Clearer branch-pin error — point at the bridge safe.directory requirement; the current message suggests the in-container fix, which does not work.

Historical Context & Trends

Metric	06-16	06-17
safe_outputs JOB hard failures	0	0
In-scope degradations	0	1 (pre-buffer)
Production PR creations	1 ✅	0 — jsweep dropped

• Production safe_outputs JOB streak unbroken (recent hard failures were all smoke-only, not exercised today).
• New finding sits at a different layer (MCP-handler/bridge) than the recurring smoke clusters — first of its kind.
• Positives: assign_to_agent clean with real numbers, 3rd consecutive (Issue Monster regexpcompileinfunction precision: isRegexpCompileCall matches the identifier name "regexp" syntactically — alias import (re "re [Content truncated due to length] #39733/uncheckedtypeassertion precision: comma-ok safe form only recognized for AssignStmt — var v, ok = x.(T) and parenthesized asse [Content truncated due to length] #39732); with-context add_labels clean again (AI Moderator [aw] Code Simplifier failed #39729); hide_comment clean on codex.
• Latent / not exercised (the 2 Smoke CI runs were push-event noop; no workflow_dispatch Smoke or PR-reviewer): target_star_review_comment_no_pr_number_fallback, add_comment_discussion_resource_not_accessible_by_integration, target_star_add_labels_no_item_number_hardfail, update_issue_target_triggering (LintMonster absent) — all remain OPEN.
• review_path_unresolved_422 Path-variant fix (pr_review_buffer.cjs:554) UNVALIDATED, 20th consecutive audit.

Metrics

• Safe Output JOB success: 100% (12/12) · Message actuation: 100% (~26 msgs)
• Most problematic: create_pull_request (0/1 intents fulfilled — bridge branch-pin)

Next Steps

• Fix the bridge branch-pin safe.directory (WI-1) — highest priority
• Watch the next daily jsweep run for recurrence
• Make report_incomplete open a tracking issue (WI-2)
• Keep monitoring latent smoke clusters on next workflow_dispatch Smoke

References:

• §27667495270 — jsweep (headline)
• §27668715568 — Issue Monster (assign clean)
• §27667076613 — AI Moderator (hide_comment + add_labels clean)

Generated by 🔒 Safe Output Health Monitor · ◷

• expires on Jun 17, 2026, 10:07 PM UTC-08:00