ci: align workflows with node 24 runtime

Author: Jacobinwwey

.github/workflows/docs-diataxis-site.yml

@@ -25,7 +25,7 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@v5
         with:
-          node-version: "20"
+          node-version: "24"
           cache: "npm"
 
       - name: Install dependencies

.github/workflows/docs-github-pages-publish.yml

@@ -56,7 +56,7 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@v5
         with:
-          node-version: "20"
+          node-version: "24"
           cache: "npm"
 
       - name: Install dependencies

.github/workflows/fixrisk-operational-readiness.yml

@@ -61,7 +61,7 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@v5
         with:
-          node-version: "20"
+          node-version: "24"
           cache: "npm"
 
       - name: Install dependencies
@@ -96,7 +96,7 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@v5
         with:
-          node-version: "20"
+          node-version: "24"
           cache: "npm"
 
       - name: Install dependencies
@@ -168,7 +168,7 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@v5
         with:
-          node-version: "20"
+          node-version: "24"
           cache: "npm"
 
       - name: Install dependencies

.github/workflows/migration-gates.yml

@@ -50,7 +50,7 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@v5
         with:
-          node-version: "20"
+          node-version: "24"
           cache: "npm"
 
       - name: Install dependencies

.github/workflows/mobile-e2e-detox-contracts.yml

@@ -23,7 +23,7 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@v5
         with:
-          node-version: "20"
+          node-version: "24"
           cache: "npm"
 
       - name: Install dependencies

.github/workflows/npm-publish.yml

@@ -40,7 +40,7 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@v5
         with:
-          node-version: "20"
+          node-version: "24"
           registry-url: "https://registry.npmjs.org"
           cache: "npm"
 

.github/workflows/release-desktop-multi-os.yml

@@ -189,7 +189,7 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@v5
         with:
-          node-version: "20"
+          node-version: "24"
           cache: "npm"
 
       - name: Setup Rust toolchain
@@ -359,7 +359,7 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@v5
         with:
-          node-version: "20"
+          node-version: "24"
           cache: "npm"
 
       - name: Setup Java 23.0.1

.github/workflows/wasm-parity-benchmark-snapshots.yml

@@ -27,7 +27,7 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@v5
         with:
-          node-version: "20"
+          node-version: "24"
           cache: "npm"
 
       - name: Install dependencies

docs/diataxis/en/explanation/development-progress-dashboard.md

@@ -484,6 +484,22 @@ Execution anchor:
   - latest published `main` runs are already green (`24703509626`, `24703509639`, `24703509627`, `24703509663`, `24703509632`),
   - this slice is recurrence hardening, not red-main incident response.
 
+## Latest Mainline Increment (2026-04-21 M8.20 Node 24 Workflow Runtime Alignment)
+
+- Root-caused the new `main` CI regression as workflow/runtime drift, not as a new learning-stack defect:
+  - failing workflow runs: `Fixrisk Operational Readiness` `24710315031`, `Migration Gates` `24710315061`,
+  - shared Windows runner symptom: `Cannot find module 'node:sqlite' from 'src/learning/store.ts'`,
+  - impact surface: `src/server.migration.test.ts`, `src/server.port.fallback.contract.test.ts`, and the aggregated fixrisk contract gate.
+- Aligned every `actions/setup-node@v5` workflow target with the runtime the repo already assumes:
+  - `.github/workflows/migration-gates.yml`,
+  - `.github/workflows/fixrisk-operational-readiness.yml`,
+  - docs/release/publish/detox/wasm workflows that were still pinned to `node-version: "20"`.
+- Closed the verifier blind spot that let FR-010 stay green while the workflow target still drifted:
+  - `scripts/verify-fixrisk-issues.js` now requires both the Node 24 force flag and an explicit `node-version: "24"` target for every workflow using `actions/setup-node`.
+- Guardrail intent remains unchanged on `main`:
+  - this is CI/runtime truth alignment, not a feature-scope expansion,
+  - FR-009 still remains operationally pending until fresh physical-device evidence is captured.
+
 ## Latest Mainline Increment (2026-04-20 M8.13 Foundation Readiness Provenance Evidence)
 
 - Added machine-readable provenance so operator tooling can tell whether readiness is reading the runtime project root or falling back to real repo evidence:

docs/diataxis/zh/explanation/development-progress-dashboard.md

@@ -484,6 +484,22 @@
   - 最新发布主线运行已经是绿色（`24703509626`、`24703509639`、`24703509627`、`24703509663`、`24703509632`），
   - 本次工作是防复发加固，不是红主线事故演戏。
 
+## 主线最新增量（2026-04-21 M8.20 Node 24 Workflow Runtime 对齐）
+
+- 已将这次新的 `main` CI 回归定位为 workflow/runtime 漂移，而不是 learning stack 新缺陷：
+  - 失败工作流运行：`Fixrisk Operational Readiness` `24710315031`、`Migration Gates` `24710315061`，
+  - 共享的 Windows runner 症状：`Cannot find module 'node:sqlite' from 'src/learning/store.ts'`，
+  - 影响面：`src/server.migration.test.ts`、`src/server.port.fallback.contract.test.ts` 与 fixrisk 聚合合同门禁。
+- 已把仓库中所有仍使用 `actions/setup-node@v5` 且残留 `node-version: "20"` 的 workflow 全部对齐到 Node 24：
+  - `.github/workflows/migration-gates.yml`，
+  - `.github/workflows/fixrisk-operational-readiness.yml`，
+  - 以及 docs/release/publish/detox/wasm 这些仍残留旧 pin 的 workflow。
+- 已补上 FR-010 verifier 的盲区，避免“文档说已升级、workflow 仍漂移”继续被误判为绿色：
+  - `scripts/verify-fixrisk-issues.js` 现在不仅要求 Node 24 force flag，也要求每个使用 `actions/setup-node` 的 workflow 显式声明 `node-version: "24"`。
+- `main` 上的护栏意图保持不变：
+  - 这次工作只是 CI/runtime 事实对齐，不是功能范围扩张，
+  - FR-009 仍然要等新的真机证据捕获后才算真正闭环。
+
 ## 主线最新增量（2026-04-20 M8.13 Foundation Readiness 来源证据）
 
 - 已新增 machine-readable provenance，执行侧现在可以直接知道 readiness 是读取 runtime project root，还是回退到真实 repo 证据：