You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
main red: dependabot updates a /website manifest that no longer exists; queen viewport readiness accepts the pill before the sectors rows it asserts #1729
Two independent root causes keep the Website checks workflow red on main (2026-10-24, run 40056405354; red on and off since 10-13):
1. Dependabot: dependency_file_not_found..github/dependabot.yml still points an npm entry at directory: "/website". The site's manifest lives at apps/website/package.json since the apps/ reorganization, so every Dependabot run on that entry fails with /website/package.json not found and the check goes red. Evidence: run 40058672529, error table dependency_file_not_found /website/package.json. The site's own dependencies have had no Dependabot PRs since the move.
2. Queen viewport matrix: the "sectors=0" readiness race.qa/queen-viewport-contract.mjs waits for readiness with live || rows === 6 but its probe asserts rows === 6 at widths above 1100 px. On the loaded gate chain the live pill answers before the sectors rows render, the wait releases, and the wars probe counts zero: run 40056405354, 1440x900 wars FAIL COUNT sectors=0, with kanban and widgets passing on the same page seconds later. The 60 s DATA_WAIT_MS comment already blames this flake (cycles 015, 035) -- the escape hatch made the wait not cover it.
The website gate failure is downstream: it is an aggregate that went red because BROWSER_B (the queen matrix job) did.
Activity