CI: node-minimum-compatibility now exceeds its 10-minute hard timeout

[huangruiteng]

症状 / Symptom

The required node-minimum-compatibility job now exceeds its hard timeout-minutes: 10 ceiling during Qualify the public minimum Node.js runtime.

• PR fix(refresh): admit checkpoint-only validator recovery #4841 run 35557447923, job 106203783165: cancelled at 10m13s with “The job has exceeded the maximum execution time of 10m0s”.
• The contemporaneous main run 35556674737, job 106201555929, fails identically at 10m16s.
• fix(refresh): admit checkpoint-only validator recovery #4841 changes only Python recovery code/tests, so this is not attributable to its diff; the same baseline failure blocks unrelated control-plane PRs.

Root cause / 根因

.github/workflows/python-tests.yml gives the minimum-Node qualification 10 minutes, while that job performs npm ci, TypeScript control-plane typecheck, and nearly the full tests/control_plane_ts/*.test.ts suite in one serial job. Current baseline duration has crossed the configured ceiling.

Desired fix / 期望修复

Keep the public Node 22.18.0 qualification intact, but restore a stable required gate by either:

1. sharding the minimum-runtime conformance tests while retaining one required aggregate receipt; or
2. as a bounded immediate repair, raising the timeout to a measured value with headroom and adding duration evidence.

Do not drop cases or convert the required gate to continue-on-error.

Acceptance / 验收

• A fresh main run and an unrelated Python-only PR complete node-minimum-compatibility.
• Node remains pinned to 22.18.0.
• The same included/excluded test contract remains enforced.
• Workflow-contract tests cover the chosen timeout/sharding semantics.

[huangruiteng]

Closing as a duplicate delivery lane of #4836. PR #4836 already raises only node-minimum-compatibility from 10 to 15 minutes, preserves Node 22.18.0 and the full non-SQLite required-gate test selection, adds workflow-contract coverage against silently dropping/sharding cases, and its exact head 1892d7f5ebea4a70e23c3e9d994f3d948eed5c7f has completed the minimum-Node job and all required checks successfully. The remaining action is independent review/merge of #4836, already tracked by the existing review/monitor lane; no second implementation PR should duplicate it.