Stop Go Logger Enhancement from calling every safe-output tool in the same run — enforce one terminal action per attempt.
Affected workflow: Go Logger Enhancement (.github/workflows/go-logger.lock.yml)
Run analyzed: §31665298469 — failed 2026-08-13T03:53:48Z, 42 turns, 20.1m duration, conclusion failure.
Baseline comparison: §31353577562 (same workflow, success, cohort-matched) made zero of the calls below.
Root cause
audit tool_usage shows create_pull_request, create_report_incomplete_issue, missing_data, missing_tool, noop, and report_incomplete each called exactly 3 times — one call to every terminal safe-output tool, repeated across all 3 harness retry attempts, instead of picking a single terminal action. The step's ##[error] annotation is not an actual error message either — its payload is a tool_result echoing raw Go source (mcp_servers.go doc comment), meaning the real failure (almost certainly the safe-outputs gateway rejecting a multi-terminal-tool call) is being masked by an unrelated buffered tool result.
Proposed remediation
- Tighten the Go Logger Enhancement prompt so it calls at most one terminal safe-output tool per attempt.
- Fix the safe-outputs gateway / log-annotation path so a multi-terminal-call rejection surfaces its own clear message under
##[error], not an unrelated buffered tool_result.
- Re-run and confirm exactly one safe-output tool fires per attempt.
Success criteria
Next scheduled Go Logger Enhancement run calls exactly one terminal safe-output tool, and any gateway rejection produces an actionable ##[error] message instead of echoed file content.
Parent: #52395
Related to #52395
Generated by 🔍 [aw] Failure Investigator (6h) · agent · 85.8 AIC · ⌖ 45 AIC · ⊞ 5.3K · ◷
Stop Go Logger Enhancement from calling every safe-output tool in the same run — enforce one terminal action per attempt.
Affected workflow: Go Logger Enhancement (
.github/workflows/go-logger.lock.yml)Run analyzed: §31665298469 — failed 2026-08-13T03:53:48Z, 42 turns, 20.1m duration, conclusion
failure.Baseline comparison: §31353577562 (same workflow, success, cohort-matched) made zero of the calls below.
Root cause
audittool_usage showscreate_pull_request,create_report_incomplete_issue,missing_data,missing_tool,noop, andreport_incompleteeach called exactly 3 times — one call to every terminal safe-output tool, repeated across all 3 harness retry attempts, instead of picking a single terminal action. The step's##[error]annotation is not an actual error message either — its payload is atool_resultechoing raw Go source (mcp_servers.godoc comment), meaning the real failure (almost certainly the safe-outputs gateway rejecting a multi-terminal-tool call) is being masked by an unrelated buffered tool result.Proposed remediation
##[error], not an unrelated buffered tool_result.Success criteria
Next scheduled Go Logger Enhancement run calls exactly one terminal safe-output tool, and any gateway rejection produces an actionable
##[error]message instead of echoed file content.Parent: #52395
Related to #52395