Upgrade Node.js setup and workflows to version 24.x

[devfrankduah]

This pull request updates the Node.js versions and the GitHub Actions used in several workflow files to ensure compatibility with the latest Node.js releases and actions. The main changes are the addition of Node.js 24.x to the test matrices and upgrading the actions/setup-node action from v4 to v6 throughout the workflows.

Workflow updates for Node.js compatibility:

• Added Node.js 24.x to the test matrices in .github/workflows/agent-review-pr.yml and .github/workflows/tests.yml, so our CI now tests against Node.js 20.x, 22.x, and 24.x. [1] [2]

• Upgraded actions/setup-node from v4 to v6 in all workflows, including .github/workflows/agent-review-pr.yml, .github/workflows/bot-respond.yml, .github/workflows/publish-release.yml, and .github/workflows/tests.yml. [1] [2] [3] [4] [5] [6]

Default Node.js version updates:

• Updated the default Node.js version used in several jobs from 20.x to 24.x, reflecting the move to the latest LTS version. This affects .github/workflows/agent-review-pr.yml, .github/workflows/bot-respond.yml, .github/workflows/publish-release.yml, and .github/workflows/tests.yml. [1] [2] [3] [4]

[llm-exe-review-bot]

Review — PR #4: Upgrade Node.js setup and workflows to version 24.x

Verdict: Approve

What was checked

Area	Status	Notes
Correctness	OK	All workflow changes are consistent — setup-node v4→v6, Node 20→24 for standalone usages, 24.x added to test matrices
dist/ freshness	N/A	No src/ changes, so no rebuild needed
action.yml contract	Unchanged	runs.using: "node20" and esbuild target remain at node20, which is correct
Security	OK	Only CI workflow config changes
Type safety	N/A	No TypeScript changes

Details

• actions/setup-node@v6 — confirmed this tag exists (latest release: v6.4.0). Valid jump from v4.
• Node.js 24.x — now the current LTS line. Good addition to test matrices while keeping 20.x and 22.x for backward compatibility.
• Test matrices (tests.yml, agent-review-pr.yml) correctly add 24.x alongside existing versions rather than replacing them.
• Standalone usages (bot-respond.yml, publish-release.yml, agent-review-pr.yml review job) bump from 20 to 24 for CI tooling — reasonable since engines: ">=20" is satisfied.

Minor note (non-blocking)

The action runtime (action.yml → runs.using: "node20") still targets Node 20. When GitHub Actions adds node22 support for the using field, you may want a follow-up PR to bump the action runtime and esbuild target as well. Not needed for this PR.

LGTM — clean CI maintenance change.

[llm-exe-review-bot]

Approved by reviewer agent (tests passing).