docs: fix EOL dates, nightly version, toolchain versions, and FUTURE_WORKFLOWS phases

Copilot · pethers · web-flow · commit 565194872f4a · 2026-05-05T20:53:07.000Z
Agent-Logs-Url: https://github.com/Hack23/game/sessions/ed6b0996-e2c8-4bc8-9bb5-f40234bfb2fe Co-authored-by: pethers <1726836+pethers@users.noreply.github.com>
diff --git a/docs/End-of-Life-Strategy.md b/docs/End-of-Life-Strategy.md
@@ -12,22 +12,22 @@ This document defines the strategy for managing Node.js runtime and TypeScript c
 
 | Node.js | Release Date | Status | Bug Fixes Until | Security Fixes Until |
 |---------|-------------|--------|-----------------|----------------------|
-| **26 (Current)** | Apr 22, 2026 | ✅ **Active — in use** | Oct 2026 | Oct 2027 |
+| **26 (Current)** | Apr 22, 2026 | ✅ **Active — in use** | Oct 2027 | Apr 2029 |
 | 25 | Oct 15, 2025 | ⚠️ Security-only | N/A | Jun 1, 2026 |
 | 24 (LTS – Krypton) | May 2025 | Active LTS | Oct 2026 | Apr 28, 2028 |
 | 22 (LTS – Jod) | Apr 2024 | Maintenance | Oct 2025 | Apr 30, 2027 |
 
-> **Note:** Node.js 26 is an even-numbered release that will graduate to **Active LTS in October 2026**. It was released on April 22, 2026. We use Node.js 27 nightly builds in the forward-compatibility workflow (`test-and-report-latest-node.yml`) to validate readiness for the next release.
+> **Note:** Node.js 26 is an even-numbered release that will graduate to **Active LTS in October 2026**. It was released on April 22, 2026. The forward-compatibility workflow (`test-and-report-latest-node.yml`) currently uses `26.0.0-nightly` to validate upcoming Node.js 26 patch releases. It will be updated to `27.0.0-nightly` once Node.js 27 nightly builds are published (expected October 2026).
 
 ### TypeScript
 
 | TypeScript | Release Date | Status | Support Until |
 |-----------|-------------|--------|---------------|
-| **6.0.2** | Mar 2026 | ✅ **Active — in use** | Until 7.0 release (~12 months) |
+| **6.0.3** | Mar 2026 | ✅ **Active — in use** | Until 7.0 release (~12 months) |
 | 5.9.x | Feb 2026 | Previous stable | Limited — security patches only |
 | 5.8.x | Dec 2025 | End of life | ❌ No support |
 
-> **Note:** TypeScript 6.0 is a major release with breaking changes including stricter module resolution with `moduleResolution: "bundler"`, removal of implicit `global` namespace, and stricter `NodeJS` namespace handling. The project uses `@typescript-eslint 8.58.0` which supports `typescript >=4.8.4 <6.1.0`.
+> **Note:** TypeScript 6.0 is a major release with breaking changes including stricter module resolution with `moduleResolution: "bundler"`, removal of implicit `global` namespace, and stricter `NodeJS` namespace handling. The project uses `@typescript-eslint 8.59.2` which supports `typescript >=4.8.4 <6.1.0`.
 
 ---
 
@@ -113,7 +113,7 @@ TS 7.0   | ~2027     | Future         | Requires @typescript-eslint update
 
 ### ✅ Completed — Upgraded to Node.js 26: May 2026
 
-All CI/CD workflows, devcontainer configuration, and `package.json` have been updated to Node.js 26. The forward-compatibility workflow (`test-and-report-latest-node.yml`) now targets Node.js 27 nightly.
+All CI/CD workflows, devcontainer configuration, and `package.json` have been updated to Node.js 26. The forward-compatibility workflow (`test-and-report-latest-node.yml`) currently uses `26.0.0-nightly` — it will switch to `27.0.0-nightly` once Node.js 27 nightly builds are published (expected October 2026).
 
 ### ⚠️ Upcoming — Node.js 25 Security EOL: June 1, 2026
 
@@ -124,11 +124,11 @@ Node.js 25 reaches full end-of-life on **June 1, 2026**. This project has alread
 When Node.js 26 enters Active LTS, it becomes the recommended production runtime. At this point:
 
 - Node.js 24 transitions from Active LTS to Maintenance LTS
-- Update `test-and-report-latest-node.yml` to Node.js 27 (already done) or 28 nightly
+- Update `test-and-report-latest-node.yml` to `27.0.0-nightly` (once available) or `28.0.0-nightly`
 
 ### 📅 Future — Node.js 27 Release: October 2026
 
-Node.js 27 will be released in **October 2026** as an odd-numbered "Current" release. The forward-compatibility workflow (`test-and-report-latest-node.yml`) already targets Node.js 27 nightly builds.
+Node.js 27 will be released in **October 2026** as an odd-numbered "Current" release (no LTS). When Node.js 27 nightly builds are published, update `test-and-report-latest-node.yml` from `26.0.0-nightly` to `27.0.0-nightly`. Primary workflows remain on Node.js 26 LTS.
 
 ### 📅 Future — Node.js 24 EOL: April 2028
 
@@ -145,7 +145,7 @@ The project maintains two parallel test workflows and tracks toolchain versions:
 | Workflow | Purpose | Current Node Version |
 |----------|---------|----------------------|
 | `test-and-report.yml` | Primary CI — stable, production-ready | **26** |
-| `test-and-report-latest-node.yml` | Forward-compat — tests next version | **27 nightly** |
+| `test-and-report-latest-node.yml` | Forward-compat — tests next version | **26 nightly** (`26.0.0-nightly`) |
 
 When a new Node.js version is released:
 1. Update `test-and-report-latest-node.yml` to the new version first
@@ -156,8 +156,8 @@ When a new Node.js version is released:
 
 | Tool | Current Version | Peer Constraint | Upgrade Path |
 |------|----------------|-----------------|-------------|
-| TypeScript | **6.0.2** | — | Follow quarterly releases |
-| @typescript-eslint | **8.58.0** | `typescript >=4.8.4 <6.1.0` | Must update before TS 6.1 |
+| TypeScript | **6.0.3** | — | Follow quarterly releases |
+| @typescript-eslint | **8.59.2** | `typescript >=4.8.4 <6.1.0` | Must update before TS 6.1 |
 | Vite | **8.0.3** | — | Follow major releases |
 | Vitest | **4.1.2** | — | Keep aligned with Vite |
 
diff --git a/docs/FUTURE_WORKFLOWS.md b/docs/FUTURE_WORKFLOWS.md
@@ -2,9 +2,9 @@
 
 ## Overview
 
-This document describes the planned upgrade of all CI/CD workflows, devcontainer configuration, and documentation from **Node.js 26** to **Node.js 27**.
+This document describes the plan to track **Node.js 27** in the forward-compatibility workflow (`test-and-report-latest-node.yml`) as a canary for the eventual **Node.js 28 LTS** upgrade.
 
-Node.js 27 is expected in **October 2026**. This upgrade plan is designed to be executed immediately after the official Node.js 27 release.
+Node.js 27 is expected in **October 2026**. Because Node.js 27 is an **odd-numbered non-LTS release**, the primary CI, devcontainer, and `package.json` will **remain on Node.js 26 LTS** throughout. Only `test-and-report-latest-node.yml` will advance to `27.0.0-nightly` once those builds are published.
 
 > **✅ Node.js 26 upgrade completed May 2026.** All workflows, devcontainer, and `package.json` have been updated. The forward-compatibility workflow (`test-and-report-latest-node.yml`) currently uses `26.0.0-nightly` (Node.js 27 nightly builds do not yet exist; they will be published once Node.js 27 development starts, expected October 2026). Update the forward-compat workflow to `27.0.0-nightly` once those builds are available.
 
@@ -25,66 +25,58 @@ Node.js 27 is an **odd-numbered** release and will **not** become LTS. We use it
 
 ## Upgrade Checklist
 
-When Node.js 27 is officially released, execute the following steps in a single PR:
+### Phase 1 — Forward-Compat Workflow (when Node.js 27 nightly builds are published)
 
-### Phase 1 — Core Configuration (Day 1)
+> **Prerequisite:** Confirm `27.0.0-nightly` builds are available on [nodejs.org/download/nightly](https://nodejs.org/download/nightly/) before running these changes.
 
-- [ ] **`package.json`** — Update `engines.node` from `>=26` to `>=27`
-- [ ] **`.devcontainer/devcontainer.json`** — Update image from `javascript-node:26-trixie` to `javascript-node:27-trixie`, and node feature version from `"26"` to `"27"`
+- [ ] **`.github/workflows/test-and-report-latest-node.yml`** — 4 occurrences: change `node-version: "26.0.0-nightly"` → `node-version: "27.0.0-nightly"` (prepare, build-validation, unit-tests, e2e-tests)
 
-### Phase 2 — GitHub Actions Workflows (Day 1)
+> **Note:** Primary workflows (`test-and-report.yml`, `release.yml`, `codeql.yml`, Copilot setup), `package.json` engines, and the devcontainer **remain on Node.js 26 LTS** for this phase. The full migration to Node.js 27 does not apply — Node.js 27 is odd-numbered and non-LTS. The next primary-workflow upgrade will happen when **Node.js 28 LTS** is released (April 2027).
 
-Update `node-version` from `"26"` to `"27"` in each of the following files:
+### Phase 2 — Documentation (same PR as Phase 1)
 
-- [ ] **`.github/workflows/test-and-report.yml`** — 4 occurrences (prepare, build-validation, unit-tests, e2e-tests)
-- [ ] **`.github/workflows/release.yml`** — 2 occurrences (prepare, build)
-- [ ] **`.github/workflows/codeql.yml`** — 1 occurrence (analyze)
-- [ ] **`.github/workflows/copilot-setup-steps.yml`** — 1 occurrence
-- [ ] **`.github/workflows/copilot-setup.yml`** — 1 occurrence in `node-version`, 1 occurrence in setup report text (`Node.js 26` → `Node.js 27`)
-- [ ] **`.github/workflows/test-and-report-latest-node.yml`** — 4 occurrences (update from `"26.0.0-nightly"` to `"27.0.0-nightly"` once Node.js 27 nightly builds are published; then advance to `"28.0.0-nightly"` once Node.js 28 nightly builds exist)
+- [ ] **`docs/End-of-Life-Strategy.md`** — Update version matrix forward-compat row to "27 nightly (`27.0.0-nightly`)", update note text
+- [ ] **`docs/WORKFLOWS.md`** — Update forward-compat Node.js version to "27 nightly"
+- [ ] **`docs/FUTURE_WORKFLOWS.md`** (this file) — Update to reflect Node.js 28 LTS as the next planned primary upgrade
 
-### Phase 3 — Documentation (Day 1–2)
+### Phase 3 — Validation (same PR)
 
-- [ ] **`docs/End-of-Life-Strategy.md`** — Update "Current Status" table, highlight Node.js 27 as active
-- [ ] **`docs/WORKFLOWS.md`** — Update "Current Node.js version" and all version references
-- [ ] **`docs/FUTURE_WORKFLOWS.md`** (this file) — Update to reflect Node.js 28 as the next planned upgrade
-- [ ] **`README.md`** — Update any Node.js version badges or requirements section if present
-
-### Phase 4 — Validation (Day 2)
-
-- [ ] Verify all CI jobs pass on the PR before merging
-- [ ] Confirm `test-and-report-latest-node.yml` passes
-- [ ] Confirm `release.yml` dry-run succeeds
-- [ ] Confirm devcontainer builds successfully with Node.js 27
-- [ ] Run `npm audit` to check for any dependency advisories under Node.js 27
-- [ ] Check `npm run test:licenses` passes
+- [ ] Verify `test-and-report-latest-node.yml` passes on the PR
+- [ ] Confirm all other CI jobs continue to pass (they all remain on Node.js 26)
+- [ ] Run `npm audit` to check for any dependency advisories
 
 ---
 
 ## Sed Commands for Automation
 
-The following commands can be run to perform the bulk of the Node.js 26 → 27 migration:
+The following command updates the forward-compat workflow to Node.js 27 nightly. Run only after confirming `27.0.0-nightly` builds are available on [nodejs.org/download/nightly](https://nodejs.org/download/nightly/):
 
 ```bash
-# Update all workflow node-version references (double-quoted)
-find .github/workflows -name "*.yml" -exec sed -i 's/node-version: "26"/node-version: "27"/g' {} +
-
 # Update the forward-compat nightly workflow from 26.0.0-nightly to 27.0.0-nightly
-# (run only after Node.js 27 nightly builds are confirmed available on nodejs.org/download/nightly)
 sed -i 's/node-version: "26.0.0-nightly"/node-version: "27.0.0-nightly"/g' .github/workflows/test-and-report-latest-node.yml
+```
 
-# Update copilot-setup.yml (single-quoted)
-sed -i "s/node-version: '26'/node-version: '27'/g" .github/workflows/copilot-setup.yml
+> **Note:** The commands below are for the **future Node.js 28 LTS upgrade** (April 2027), not for Node.js 27. Primary workflows, `package.json`, and the devcontainer stay on Node.js 26 until Node.js 28 LTS.
 
-# Update text references
-sed -i 's/Node\.js 26/Node.js 27/g' .github/workflows/copilot-setup.yml
+```bash
+# === Node.js 28 LTS upgrade (April 2027) — DO NOT run for Node.js 27 ===
+
+# Update all workflow node-version references (double-quoted)
+find .github/workflows -name "*.yml" -exec sed -i 's/node-version: "26"/node-version: "28"/g' {} +
+
+# Update the forward-compat nightly to 28.0.0-nightly (once available)
+sed -i 's/node-version: "27.0.0-nightly"/node-version: "28.0.0-nightly"/g' .github/workflows/test-and-report-latest-node.yml
+
+# Update copilot-setup.yml (single-quoted)
+sed -i "s/node-version: '26'/node-version: '28'/g" .github/workflows/copilot-setup.yml
+sed -i 's/Node\.js 26/Node.js 28/g' .github/workflows/copilot-setup.yml
 
 # Update package.json engines field
-sed -i 's/"node": ">=26"/"node": ">=27"/' package.json
+sed -i 's/"node": ">=26"/"node": ">=28"/' package.json
 
 # Update devcontainer image
-sed -i 's/javascript-node:26-trixie/javascript-node:27-trixie/' .devcontainer/devcontainer.json
-sed -i 's/"version": "26"/"version": "27"/' .devcontainer/devcontainer.json
+sed -i 's/javascript-node:26-trixie/javascript-node:28-trixie/' .devcontainer/devcontainer.json
+sed -i 's/"version": "26"/"version": "28"/' .devcontainer/devcontainer.json
 ```
 
 ---
