Fix spurious error annotations in safe_outputs jobs from GraphQL diagnostic logging

[Copilot]

The update_project safe output was generating 10+ error annotations in GitHub Actions UI for successful workflow runs. The logGraphQLError() function used core.error() for diagnostic information, creating false error annotations despite job success.

Changes

• Changed logGraphQLError() in pkg/workflow/js/update_project.cjs to use core.info() for diagnostic output
• Preserved core.error() for actual operation failures
• Recompiled workflows to propagate the fix

Impact

Diagnostic information (error details, request/response data, permission troubleshooting) now appears in job logs without creating error annotations. Actual failures that prevent operation completion still generate appropriate error annotations.

Before:

function logGraphQLError(error, operation) {
  core.error(`GraphQL Error during: ${operation}`);
  core.error(`Message: ${error.message}`);
  // ... more core.error() calls for diagnostics
}
// Result: 10+ error annotations in UI

After:

function logGraphQLError(error, operation) {
  core.info(`GraphQL Error during: ${operation}`);
  core.info(`Message: ${error.message}`);
  // ... diagnostic details logged as info
}
// Result: Clean UI, diagnostics still visible in logs

Original prompt

Analyze safe output erros in run: https://github.com/githubnext/gh-aw/actions/runs/20365622919/job/58520092414

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.