09-03 moved the application graph behind a dynamic import, but only jsdom
checked it. A real production build whose installed messages collide now
opens in a browser and must show the boot error shell, not the loading shell.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Old-tab chunk recovery in the default configuration only had jsdom tests, and
the old-asset test checked its own hosting fixture. A spec now serves two real
builds: the old tab reloads once into the new one and not a second time. The
fixture test and the acceptance row now say what they cover.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The route spec only checked that the protected screen opened, so a schema
violating 200 or a 503 still passed it. It now asserts the mocked row, and
a new spec saves once and retries after a 429 in a real browser.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
check:test-evidence requires every e2e spec to use the strict fixture, which
fails on the zod eval console error. The smoke now sets zod's global config
jitless before page scripts run and requires zero violations; without that
init script it fails on the known probe.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The declared CSP was never applied in a browser. A Playwright spec now serves
the build with config/hosting/security-headers.json and fails on any
securitypolicyviolation. It found one: zod's Function('') probe, listed in the
spec as a known violation until zod is configured jitless before first use.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
check:adapter-inventory forbids a raw node_modules symlink in fixtures; use
linkFixtureNodeModules like the other fixture builders.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
vite.service-worker.config.ts loaded .generated/frontend-runtime/*.ts with a
bare relative import(). Vite's default `bundle` config loader runs the config
from node_modules/.vite-temp/, so with the ACTIVE selection
`corepack pnpm build` stopped at the worker step. Resolve the paths against
import.meta.url, which every loader keeps pointing at the config file.
The e2e helper no longer patches build-frontend.ts with
`--configLoader native`; the quarantined fixme is replaced by a check that
both unmodified ACTIVE builds emitted service-worker.js.
RED (throwaway copy, ACTIVE selection, unmodified scripts/build-frontend.ts):
TypeError: Required generated module is unavailable:
./.generated/frontend-runtime/service-worker-assets.ts
[cause]: Error [ERR_MODULE_NOT_FOUND]: Cannot find module
'.../node_modules/.vite-temp/.generated/frontend-runtime/service-worker-assets.ts'
build step failed: npx vite build --config vite.service-worker.config.ts
build-frontend exit=1
GREEN: same copy after the fix -> build-frontend exit=0, dist/service-worker.js
emitted; `pnpm test:e2e --project=chromium
tests/e2e/service-worker-update.spec.ts` 5 passed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Builds the app twice with the ACTIVE selection in a temp copy and serves
either dist from a per-test static server. Covers install with
application/javascript and gzip bodies, update-waiting/reload-required
through the host, and the previous-cache fallback for a removed chunk.
The unmodified ACTIVE build fails (vite.service-worker.config.ts resolves
.generated/ from node_modules/.vite-temp); that case is test.fixme and the
helper builds with --configLoader native.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>