The deploy-floor CI lane builds the bundle it certifies but never boots it #196

Status, 2026-09-27

Done: the boot check exists in-repo. tests/browser/smoke.mjs waits for #app and asserts the Press any key title sentinel. deploy-pages.yml runs it and the tests/e2e suite before publishing, and pr-preview.yml runs it on PRs labelled deploy-preview. The Playwright scripts the body below points at live outside this repo.

To close this issue:

• Run tests/browser/smoke.mjs against the bundle in test.yml's pinned lane, after the WASM build smoke step (l.112), which builds the bundle and never loads it. No branch or PR for this exists yet.
• Decide whether the latest (upstream smoke test) lane gets the same step (it is continue-on-error, per the Scope section below).

pinned (deploy floor) in test.yml resolves .let-go-version, installs that let-go, compiles each test namespace, runs xsofy/test/run.lg, and runs the Layer-1 runtime smoke. It never runs make wasm, and never loads the result.

deploy-pages.yml resolves the same .let-go-version and builds the WASM bundle with it. So the lane named for the deploy floor exercises a different thing than the deploy does, and a let-go version that cannot build a working bundle passes it.

That is not hypothetical. The pin was stale in exactly that way until #195: on cf195a67, all three lane steps pass, and the bundle they certify dies at namespace load.

error loading xsofy.input: ExecutionError: calling dev?
  caused by bit-shift-left expected Int

Reproduced 3 runs out of 3 in headless Chromium under COI headers. The suite was green the whole time, because nothing in it builds the bundle. The gap had been open since 2026-07-16, when the SHA pin landed.

Suggested check

Two steps at the end of the pinned lane:

1. make wasm — the id="app" guard already in the Makefile catches a stale builder, but only if something runs it in CI.
2. Load dist/index.html in a headless browser with Cross-Origin-Opener-Policy: same-origin and Cross-Origin-Embedder-Policy: require-corp, and fail on a page error or a missing title sentinel.

The COI headers are load-bearing: lg's wasm input ring is SharedArrayBuffer backed, so a plain static server boots to a read-key failure rather than the game, and the bundled coi-serviceworker.js fallback is not reliable under headless automation. local-scripts/coi-serve.py in the joint workspace exists for this, and the repo already carries Playwright smoke scripts under local-scripts/browser-smoke-playwright/ that could host the check.

Worth knowing if you reuse smoke.mjs as the starting point: it still waits for #terminal, which #378 renamed to #app, so it would need that one-line update to be meaningful against a current bundle.

Scope

This is about the floor lane specifically. The latest (upstream smoke test) lane has the same shape, and would benefit from the same two steps, but it is continue-on-error so a gap there is cheaper.

Happy to open the PR if the shape above looks right, or to take a different one if you would rather the boot check live in its own workflow than extend the matrix.