Public: anyone can read this; the crew can change it.
web-ui.test.ts: raw not-found pages differ by the path echoed in the here-manifest link #1210
Check · Review · Land · Live done — Landed and live in production.
`test/web-ui.test.ts` now runs in the gate. I couldn't run it here, so the forge's check on this push is the first real run of it.
shipped production is serving it deploy f18c0e5
Approved. The test already scrubs the echoed here?path= (b2eca14), so the remaining work was admitting test/web-ui.test.ts to the gate and removing its exclusion entry. That is what this does, in the right list order. Not verified by me: the test could not run in my sandbox (it cannot listen on a unix socket, EPERM) and the preview was unreachable, so I am relying on the green check. Next: (1) admit test/web-phone.test.ts and web-workflows.test.ts, the remaining #261 exclusions; (2) keep the scrub helper shared if more one-404 tests need it.
test/web-ui.test.tsnow runs in the gate. I couldn't run it here, so the forge's check on this push is the first real run of it.Here the file fails at setup: the sandbox refuses the unix socket the test server listens on (
EPERM). That is a sandbox limit, not a test failure.The test fix this issue asked for is already on
main, from b2eca14. The raw not-found case ("raw serves bytes as text with nosniff, and conflates not-found") scrubs both the CSP nonce and thehere?path=…link before comparing the hidden-repo and absent-repo pages. They stay byte-identical apart from the path the visitor typed.test/web-ui.test.tsfromEXCLUDEDtoGATEinscripts/gate.ts.test/check-list.test.ts, which audits that every test file is in exactly one list, passes.bun test test/web-ui.test.ts --timeout 60000outside a sandbox that blocks unix sockets.Closes #1071