startup-failure-capture-acceptance.json

1{
2  "sourceBase": "e4cb86bec470d222b89dd250849230e7963ce3ce",
3  "sourceFilesSha256": {
4    "tests/browser/multiplayer.spec.ts": "d31481b474c3775b59ae99f219a26164c2db4badbe2e2d2045f049303842bb58"
5  },
6  "scope": "Capture startup stage and DOM diagnostics from the actual failed Enter page before context teardown. Production code, deadlines, graphics quality and motion contracts unchanged.",
7  "checks": {
8    "typecheck": true,
9    "sourceBoundaries": 74
10  },
11  "diagnosticRegression": {
12    "startTime": "2026-10-25T04:03:29.640Z",
13    "duration": 37338.274,
14    "expected": 1,
15    "skipped": 0,
16    "unexpected": 0,
17    "flaky": 0
18  },
19  "twoCpuJourney": {
20    "startTime": "2026-10-25T04:02:08.966Z",
21    "duration": 41586.043000000005,
22    "expected": 1,
23    "skipped": 0,
24    "unexpected": 0,
25    "flaky": 0
26  },
27  "twoCpuCommand": "CI=1 PLAYWRIGHT_EXECUTABLE_PATH=/tmp/dw-browser-test/chrome-linux/headless_shell taskset -c 0,1 npm run test:browser -- tests/browser/multiplayer.spec.ts --grep \"two real browsers share doors\"",
28  "findings": [
29    "A held native GPU request in the second real client produces its own device-stage timeout report, including completed room and simulation stages.",
30    "The healthy observer remains connected and playable; its separate report has a completed startup.",
31    "The unmodified door/chat/handoff scenario passed under two-CPU affinity. CPU count alone did not reproduce the remote failure."
32  ],
33  "limits": [
34    "The held GPU is a deliberate diagnostic fault, not an explanation for the CI stall.",
35    "The local workstation and GitHub runner are not equivalent hardware.",
36    "Remote second-player native initialization remains unresolved pending the new failing-page reports."
37  ]
38}
39