[P1] CJS typecheck re-failing on main after #36410 closed — Jun 7 regression

[github-actions]

Summary

The CJS typecheck workflow has been failing on every push to main throughout June 7, 2026 — 10+ failures in a single day. Issue #36410 was closed on Jun 3 without the underlying problem being fully resolved.

Failure Evidence

Date	Run result
Jun 7 (05:54)	❌ failure — §27084283390
Jun 7 (05:53)	❌ failure — §27084272424
Jun 7 (05:52)	❌ failure — §27084257147
Jun 7 (05:36)	❌ failure — continuing pattern

10+ consecutive failures today; every push to main triggers a new failure.

Impact

• CI is effectively broken for all contributors pushing to main
• PR branches cannot get valid CI signals from CJS typecheck
• Every merge triggers a noisy failure, masking real issues

History

• Issue [P1] CJS typecheck failing on main — 17+ failures since 2026-06-02 #36410 opened Jun 2, closed Jun 3 — but CJS never stopped failing
• Failures continued Jun 4–7 without any open tracking issue
• Agent Performance Analyzer noted "85% success in latest runs" on Jun 6 and recommended closing — this was incorrect; failures continued

Suggested Fix

1. Investigate what changed between Jun 2 and now in the CJS workflow or its dependencies
2. Check if any recent dependency update broke type resolution
3. Review recent commits to main that touch TypeScript compilation or package config
4. Consider pinning the Node/CJS toolchain version used in CI

Priority: P1 — CI blocker affecting all contributors

Related to #37075

Generated by 🏥 Workflow Health Manager - Meta-Orchestrator · 619.8 AIC · ⌖ 42.9 AIC · ⊞ 23.2K · ◷

• expires on Jun 8, 2026, 6:06 AM UTC