Accidentally submitted the create_pull_request call with a placeholder title/body while testing a permission denial; the per-run limit (1) is now exhausted so the correct content could not be sent.
Adds targeted debug logging (`pkg/logger`) to two files from the candidate manifest pool that already had a package logger declared but were missing coverage on real failure/branch paths:
- **`pkg/cli/actionlint.go`**: logs git-root resolution failure, the start/end of the `docker run` invocation (with timeout and stdout/stderr byte counts), and the timeout/cancellation branches in `actionlintContextError`. These are the paths most likely to need `DEBUG=cli:actionlint` troubleshooting (Docker/network issues, hangs, cancellation).
- **`pkg/cli/add_interactive_schedule.go`**: logs the entry point and each early-return branch of `detectWorkflowScheduleInfo` (missing/unparseable frontmatter, no `on:` trigger, unrecognized schedule expression) so it's possible to tell why the add-wizard didn't offer a schedule-frequency prompt for a given workflow.
## Note on candidate selection
Most files in the pre-flight manifest's `files_needing_logger` pool (e.g. the rest of `pkg/actionpins`, `pkg/agentdrain`, and most of the sampled `pkg/cli` package-manifest files) already have thorough, non-duplicative logging via existing package-level loggers (`actionPinsLog`, `addPackageManifestLog`, `addInteractiveLog`, etc.) — the manifest's pool appears to be a broad, largely unfiltered candidate list rather than a precise "needs logging" signal. Per the task's own quality guidance ("no duplicate logging with existing logs", "quality over quantity"), I sampled roughly 20 files from the pool and only added logging where I found genuine, non-trivial control-flow gaps, rather than padding to 5 files with low-value or duplicate log calls.
## Validation
- `make build && make fmt` passed.
🤖 Generated with [Claude Code]((claude.com/redacted)
Workflow Failure
Workflow: Go Logger Enhancement
Branch: main
Run: https://github.com/github/gh-aw/actions/runs/37723178880
Warning
Task Could Not Be Completed: The agent reported that the task could not be performed due to an infrastructure or tool failure.
Error details:
This is a structured incompletion signal (
report_incomplete), not a real task outcome. Any other safe outputs emitted alongside this signal (e.g., comments) describe the failure state, not a completed review or action.Action Required
Assign this issue to an agent to debug and fix the issue.
Debug with any coding agent
Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.):
Manually invoke the agent
Debug this workflow failure using your favorite Agent CLI and the
agentic-workflowsprompt.agentic-workflowsskill from.github/skills/agentic-workflows/SKILL.mdor https://github.com/github/gh-aw/blob/main/.github/skills/agentic-workflows/SKILL.mddebug the agentic workflow go-logger failure in https://github.com/github/gh-aw/actions/runs/37723178880Tip
Stop reporting this workflow as a failure
To stop a workflow from creating failure issues, set
report-failure-as-issue: falsein its frontmatter: