[plan] Debug and fix high-error workflows

[github-actions]

Objective

Investigate and fix three workflows with exceptionally high error rates that indicate fundamental configuration or permission issues, saving $15-20/month in wasted operations.

Context

Three workflows have error rates indicating they are broken or severely misconfigured:

• Security Fix PR: 44.3 errors/run (753 total errors in 17 runs)
• Go Logger Enhancement: 45.6 errors/run (228 errors in 5 runs)
• Dev Hawk: 20.6 errors/run (556 errors in 27 runs)

These errors waste compute resources and indicate underlying problems that need resolution.

Investigation Steps

1. Security Fix PR (44 errors/run)

File: .github/workflows/security-fix-pr.md (or similar)

Actions:

1. Review recent workflow run logs in GitHub Actions UI
2. Check for common error patterns:
   • Permission denied errors
   • Missing tool errors
   • Authentication failures
   • Network access issues
3. Examine workflow configuration for:
   • Incorrect permissions in frontmatter
   • Missing required tools
   • Invalid network/firewall rules
4. Fix or disable workflow until issue resolved

2. Go Logger Enhancement (45.6 errors/run)

File: .github/workflows/go-logger-enhancement.md (or similar)

Actions:

1. This has the highest error rate - likely completely broken
2. Check if this is a test/development workflow that should be removed
3. Review error logs to determine root cause
4. Either fix configuration or remove workflow if obsolete

3. Dev Hawk (20.6 errors/run)

File: .github/workflows/dev-hawk.md

Actions:

1. Review error patterns in recent runs
2. Common issues to check:
   • GitHub API permission problems
   • Tool access restrictions
   • Safe output configuration errors
3. Update workflow configuration to resolve issues

Debugging Resources

Log Locations:

• GitHub Actions UI: Repository → Actions → Select workflow run
• Agent stdio logs: Look for agent-stdio.log in workflow artifacts
• Error summaries: Check workflow run annotations

Common Fixes:

• Add missing permissions in frontmatter
• Configure required tools in tools: section
• Fix network access rules in network: section
• Update safe output configurations

Implementation Steps

1. For each workflow, review at least 3 recent failed/error-heavy runs
2. Document error patterns and root causes
3. Apply appropriate fixes to workflow configuration
4. Test fix by triggering a manual run
5. If unable to fix quickly, disable workflow to stop cost waste
6. Run make recompile after any configuration changes

Acceptance Criteria

• Security Fix PR: Error rate reduced below 5/run OR workflow disabled
• Go Logger Enhancement: Error rate reduced below 5/run OR workflow disabled
• Dev Hawk: Error rate reduced below 5/run
• Root causes documented in issue comments
• All fixes tested with successful workflow runs
• Cost savings of $15-20/month realized

Expected Impact

• Savings: $15-20/month from reduced wasted operations
• Reliability: Improved workflow success rates
• Reduced Noise: Fewer spurious errors in monitoring
  Related to [plan] Optimize workflow costs - Reduce monthly spend by 18-26% #7331

AI generated by Plan Command for discussion #7231