npm run test:gate stalls in npm run test:integration / vitest run --config vitest.integration.config.ts on Windows after the 136-file unit suite passes (3,887 tests). src/App.test.tsx is the only integration file. On 2026-09-27, the Vitest worker stayed CPU-active for over three minutes, with no result or timeout report; the run was stopped. This is independent of the #659 C++/WinUI roster change and blocks a complete gate report.
Repro: npm run test:gate on Windows from f63bf743 plus #659 branch changes. The integration config has testTimeout: 30_000, hookTimeout: 30_000, one forked worker. Expected: tests finish or fail with a diagnostic within the configured timeout. Actual: worker remains busy without output.
Investigate the App integration test's setup/render loop and restore a bounded pass/fail result. Rank remains with the owner; this is unranked intake, not a change to docs/BACKLOG.md.
npm run test:gatestalls innpm run test:integration/vitest run --config vitest.integration.config.tson Windows after the 136-file unit suite passes (3,887 tests).src/App.test.tsxis the only integration file. On 2026-09-27, the Vitest worker stayed CPU-active for over three minutes, with no result or timeout report; the run was stopped. This is independent of the #659 C++/WinUI roster change and blocks a complete gate report.Repro:
npm run test:gateon Windows fromf63bf743plus #659 branch changes. The integration config hastestTimeout: 30_000,hookTimeout: 30_000, one forked worker. Expected: tests finish or fail with a diagnostic within the configured timeout. Actual: worker remains busy without output.Investigate the App integration test's setup/render loop and restore a bounded pass/fail result. Rank remains with the owner; this is unranked intake, not a change to
docs/BACKLOG.md.