Summary

• Fixes the "Write job summary" step which was still failing with backticks in agent output
• Uses environment variables + printf instead of direct interpolation with echo

Problem

After #9425 fixed the "Update Check Run" step, the "Write job summary" step was still failing with:

syntax error near unexpected token `newline'

This happened because backticks in the agent output (like `<!-- Testing -->`) were being interpreted as bash command substitution when using:

echo "${{ steps.run.outputs.output }}"

Solution

Same pattern as the previous fix:

1. Pass outputs as environment variables
2. Use printf '%s\n' "$VAR" instead of echo "$VAR" to avoid any special character interpretation

Test plan

• Verified locally that printf correctly handles backticks, quotes, and other special characters
• Re-run the failing workflow to confirm

🤖 Generated with Claude Code

Summary by cubic

Fix string handling in GitHub workflows to safely handle backticks, quotes, and other special characters and prevent syntax errors.
The job summary now uses env vars and printf; the Check Run step reads the agent name from env; and the agents API request uses jq to build JSON safely.

^{Written for commit 2d21472. Summary will update on new commits.}