chore(ci): Update flaky windows CI analysis doc (root cause found)

[Tobbe]

Reported on Node here: nodejs/node#62260

[netlify]

✅ Deploy Preview for cedarjs ready!

Name	Link
🔨 Latest commit	d85a7c4
🔍 Latest deploy log	https://app.netlify.com/projects/cedarjs/deploys/6a0383929442e200082e9837
😎 Deploy Preview	https://deploy-preview-1763--cedarjs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[greptile-apps]

Greptile Summary

This PR updates the flaky Windows CI investigation document with the identified root cause of the STATUS_STACK_BUFFER_OVERRUN crashes: V8's Maglev JIT compiler (enabled by default in Node 20.11+) produces stack-corrupting native code on Windows, affecting both the React 18 and React 19 smoke test tracks on Node 24.

• Adds a detailed chronology of a cedar dev crash triggered during Vite dependency re-optimization, with per-test failure breakdown showing 3 pre-crash passes and 12 post-crash failures.
• Documents the upstream Node.js issue (nodejs/node#62260) and Chromium tracker bug as the confirmed root cause, explains why Cedar's CI is specifically affected, and provides a short-term --no-maglev workaround plus a long-term monitoring plan.

Confidence Score: 5/5

This is a documentation-only change with no code modifications; merging carries no runtime risk.

The change appends investigation notes and mitigation guidance to a markdown file. No production code, CI configuration, or build scripts are touched, so there is nothing that can regress.

No files require special attention.

Important Files Changed

Filename	Overview
docs/implementation-plans/flaky-windows-smoke-tests-investigation.md	Adds ~197 lines of investigation findings: V8 Maglev JIT root cause, crash chronology, and --no-maglev mitigation guidance. Internally consistent; no contradictions in the current diff.

_{Reviews (2): Last reviewed commit: "fix greptile review comments" | Re-trigger Greptile}

[nx-cloud]

🤖 Nx Cloud AI Fix

Ensure the fix-ci command is configured to always run in your CI pipeline to get automatic fixes in future runs. For more information, please see https://nx.dev/ci/features/self-healing-ci

---

View your CI Pipeline Execution ↗ for commit d85a7c4

Command	Status	Duration	Result
nx run-many -t build:pack --exclude create-ceda...	✅ Succeeded	3s	View ↗
nx run-many -t build	✅ Succeeded	<1s	View ↗

---

☁️ Nx Cloud last updated this comment at 2026-05-12 19:53:01 UTC