Summary

• Fixes JavaScript parsing errors in the continue-agents.yml workflow when agent output contains special characters
• Changes the "Update Check Run" step to use environment variables instead of direct string interpolation

Problem

The workflow was failing with errors like SyntaxError: Unexpected identifier 'mobile' because agent output was being interpolated directly into JavaScript template literals:

const output = `${{ steps.run.outputs.output }}`;  // ❌ Breaks with special chars

When the output contains backticks, ${} sequences, or certain line breaks, it breaks the JavaScript syntax.

Solution

Pass outputs as environment variables and access them via process.env:

env:
  AGENT_OUTPUT: ${{ steps.run.outputs.output }}

const output = process.env.AGENT_OUTPUT || '';  // ✅ Safe handling

Environment variables are passed as-is without string parsing issues.

Test plan

• Verified locally that env var approach correctly handles: multi-line text, backticks, template literal syntax, quotes
• Re-run the failing workflow in remote-config-server to confirm the fix

🤖 Generated with Claude Code

Summary by cubic

Use environment variables in the continue-agents workflow to safely handle agent output and prevent JavaScript parsing errors. This avoids failures when output includes backticks, ${}, or multi-line content and ensures the check run updates reliably.

• Bug Fixes
  • Pass outputs as env vars: AGENT_OUTPUT, AGENT_ERROR, AGENT_SUCCESS, CHECK_RUN_ID.
  • Read values via process.env and parse CHECK_RUN_ID as an integer.
  • Remove template-literal interpolation to avoid syntax errors from special characters.

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