[P1] Recurring `node: command not found` on aw-gpu-runner-T4 (Daily News, Daily Issues Report)

[github-actions]

Problem Statement

Two Copilot-engine workflows running on aw-gpu-runner-T4 are failing with /bin/bash: line 1: node: command not found. This error is recurring across multiple days (observed Apr 19 and Apr 20, 2026).

Affected Workflows

Workflow	Run	Date	Error
Daily News	§24658469657	Apr 20	node: command not found
Daily Issues Report Generator	§24662146658	Apr 20	node: command not found
Daily News	#27165 (yesterday)	Apr 19	same pattern

Root Cause Hypothesis

Both workflows run on aw-gpu-runner-T4 with the Copilot engine (engine.bare: true or engine: copilot). The Copilot engine terminates with the error after the agent startup succeeds, suggesting Node.js is expected to be available in $PATH during agent execution but is missing on this GPU runner image.

• daily-news specifies network.allowed: [node] (network access, not runtime)
• daily-issues-report specifies runtimes.node.version: "24" — this should install Node.js 24 via the Setup Node.js action, but the error suggests it's not being found in shell execution context.

Possible causes:

1. aw-gpu-runner-T4 does not have Node.js pre-installed and the runtime PATH is not propagating to bash subshells
2. The Copilot CLI is trying to invoke node for internal operations before the runtime is properly set up
3. A recent change to the aw-gpu-runner-T4 image removed Node.js from default PATH

Proposed Remediation

1. Verify runner image: Check whether aw-gpu-runner-T4 has Node.js installed by default (run which node && node --version as a workflow step)
2. Check PATH propagation: Ensure the setup-node action's PATH additions persist to subsequent bash steps
3. Add explicit Node.js setup step: Add an explicit uses: actions/setup-node@v4 step before agent execution for workflows requiring Node.js on GPU runners
4. Consider migrating to ubuntu-latest: If Node.js is not needed for GPU computation in these workflows, switching to ubuntu-latest runner (which has Node.js pre-installed) may resolve the issue

Success Criteria

Both Daily News and Daily Issues Report Generator complete without node: command not found errors on next scheduled run.

References

• Daily News failure: [aw] Daily News failed #27295
• Daily Issues Report failure: [aw] Daily Issues Report Generator failed #27301
• Also observed Apr 19: [aw] Daily Issues Report Generator failed #27165

References:

• §24658469657
• §24662146658

Note

🔒 Integrity filter blocked 5 items

The following items were blocked because they don't meet the GitHub integrity level.

• #19099 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #21784 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #27282 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #27260 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #27259 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by Workflow Health Manager - Meta-Orchestrator · ● 3.6M · ◷

• expires on Apr 21, 2026, 12:25 PM UTC

[github-actions]

🍪 *Issue Monster selected this for Copilotecho BEGIN___COMMAND_OUTPUT_MARKER ; PS1= ; PS2= ; unset HISTFILE ; EC=0 ; echo ___BEGIN___COMMAND_DONE_MARKER___0 ; }

I've identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent.

If assignment succeeds, the Copilot coding agent will analyze the issue and create a pull request with the fix.

Om nom nom! 🍪> [!CAUTION]

Security scanning requires review for Issue Monster

Details

Potential security threats were detected in the agent output. The workflow output should be reviewed before merging.

Review the workflow run logs for details.

🍪 Om nom nom by Issue Monster · ● 21.2K · ◷

[pelikhan]

@copilot fix the agentic workflows by enable the node runtime in the front matter of the workflows using this runner