fix(ci): pin Node 24 LTS repo-wide; fix CommonJS scripts crashing under ESM

[eleshar]

Summary

Targets #2351 (release/v1.0.0). Prompted by the CI failure on handle-issue-labeled.js (ReferenceError: require is not defined in ES module scope) plus the follow-up note that the runner was still on an out-of-date Node version.

1. Node version drift — .nvmrc said 22, package.jsonengines said >=18, and workflows individually hardcoded "18"/"20"/"22"/"lts/*" for setup-node (including "20", which GitHub is deprecating on hosted runners). Checked nodejs.org's current release schedule: Node 24 is the current Active LTS. Standardised on 24 everywhere — .nvmrc, package.jsonengines.node, and every hardcoded node-version across .github/workflows/ and workflows/. Confirmed no workflow runs a Node version matrix, so a blanket normalise was safe.

2. The actual crash — package.json declares "type": "module", so every .js file is parsed as ESM; a .js file using require()/module.exports throws at the first require() call, at runtime, not at CI-lint time — which is why this shipped and only surfaced when a workflow actually executed the path. Found 17 such files by cross-referencing every node scripts/....js invocation across all workflows against which targets still contain require() with no import/export. Renamed all 17 to .cjs (explicit CommonJS marker — the standard fix, no logic changes) and updated every run: node ... call and in-script require(...) path that pointed at them (including inside actions/github-script blocks).

Left alone:scripts/agents/planner.agent.js and issues.agent.js were also flagged as CommonJS-under-ESM, and an existing test (module-system-consistency.test.js) shows the intended fix for this specific directory is proper ESM conversion, not extension renaming — so those were renamed to .cjs as a consistent, working fix for now, but converting them to native ESM (matching reviewer.agent.js's existing pattern) would better match the codebase's own stated intent; flagging as a follow-up rather than doing a larger rewrite in this fix. Also caught and reverted a false-positive: my rename script's word-boundary match briefly touched an unrelated docblock reference in task-planner.agent.js (a stub, never actually invoked, whose name is a substring match on "planner.agent.js") — restored to its original text.

Test plan

• CI passes on this branch — specifically handle-issue-labeled.js's call path (openspec-progress-phase.yml) and the other 6 renamed handlers
• Confirm actions/setup-node@v7 with node-version: "24" resolves and installs cleanly on hosted runners
• Follow-up issue: convert scripts/agents/planner.agent.cjs and issues.agent.cjs to native ESM, matching reviewer.agent.js and the existing module-system-consistency test's intent

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

🗂️ Base branches to auto review (5)

• main
• develop
• feature/*
• fix/*
• update/*

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: CHILL

Plan: Pro Plus

Run ID: 7ed564c6-bd24-4211-b030-bac875852f81

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Note

.coderabbit.yml has unrecognized properties

CodeRabbit is using all valid settings from your configuration. Unrecognized properties (listed below) have been ignored and may indicate typos or deprecated fields that can be removed.

⚠️ Parsing warnings (1)

Validation error: Unrecognized keys: "auto_labels", "auto_assign", "auto_review"

⚙️ Configuration instructions

• Please see the configuration documentation for more information.
• You can also validate your configuration using the online YAML validator.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

🚫 This PR description is missing required template content.

Missing required section(s): Linked issues, Changelog, Global DoD checklist

Please update the PR body using one of the repository PR templates:

• https://github.com/lightspeedwp/.github/blob/develop/.github/pull_request_template.md
• https://github.com/lightspeedwp/.github/tree/develop/.github/PULL_REQUEST_TEMPLATE

Empty placeholders, unchecked checklist boxes, and stub issue references do not count.

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-08-27 11:28 UTC · Rule: dependabot-develop · triggered by merge protections
• ✅ Checks skipped · PR is already up-to-date
• ✅ Merged — 2026-08-27 11:28 UTC · at 8e7cb53e87c5feb8bf08a9834d824af28f107262 · squash

This pull request spent 19 seconds in the queue, including 1 second running CI.

Required conditions to merge

[github-actions]

Milestone Allocation

node:internal/modules/package_json_reader:301
throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null);
^
Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'octokit' imported from /home/runner/work/.github/.github/scripts/automation/allocate-to-milestone.js
at Object.getPackageJSONURL (node:internal/modules/package_json_reader:301:9)
at packageResolve (node:internal/modules/esm/resolve:768:81)
at moduleResolve (node:internal/modules/esm/resolve:859:18)
at defaultResolve (node:internal/modules/esm/resolve:992:11)
at #cachedDefaultResolve (node:internal/modules/esm/loader:701:20)
at #resolveAndMaybeBlockOnLoaderThread (node:internal/modules/esm/loader:721:38)
at ModuleLoader.resolveSync (node:internal/modules/esm/loader:759:56)
at #resolve (node:internal/modules/esm/loader:683:17)
at ModuleLoader.getOrCreateModuleJob (node:internal/modules/esm/loader:603:35)
at ModuleJob.syncLink (node:internal/modules/esm/module_job:163:33) {
code: 'ERR_MODULE_NOT_FOUND'
}
Node.js v24.19.0