Skip to content

deltic-browser rows: composed artifacts runtime-linked in Chromium - #39

Merged
lann merged 2 commits into
mainfrom
deltic-browser
Aug 10, 2026
Merged

deltic-browser rows: composed artifacts runtime-linked in Chromium#39
lann merged 2 commits into
mainfrom
deltic-browser

Conversation

@lann

@lann lann commented Aug 10, 2026

Copy link
Copy Markdown
Collaborator

The browser half of the deltic legs (lann/deltic#14): deltic-browser + deltic-browser-delegated run both composed artifacts inside headless Chromium through the upstream page driver and polymorph-test's deltic worker — the pinned deltic-embedder.mjs release asset links the suite in the browser. No transpile step, no generated tree; the artifacts import only wasi 0.2 + test-context, so the stock upstream worker serves the leg unmodified. This repo's frame: asset wiring, target config, results writing (driver-ct/deltic/run-browser.mjs, own npm tree — no jco dependency).

Co-dependent (named per the sizing rule): the component-test pin moves to b402686 (the deltic worker ships there). That repo is jco-free and deleted its component-test-jco-transpile bin, so the thin wrapper is vendored into driver-ct/jco/ — it resolves this repo's own pinned jco-transpile and retires with the jco tree.

Matrix: 11 targets, 70 results, 0 failing — deltic-browser rows identical to jco-browser case for case. First-order perf (same box, warm): jco-browser 2.4 s, deltic-browser 2.7 s wall for both compositions.

Gates: just check; conformance-ct::all with CONFORMANCE_BROWSER=1; matrix-check green.

lann added 2 commits August 10, 2026 13:51
…m; component-test to b402686

The browser half of the deltic legs (lann/deltic#14): deltic-browser +
deltic-browser-delegated run both composed artifacts inside headless
Chromium through the upstream page driver and polymorph-test's DELTIC
worker — the pinned deltic-embedder.mjs release asset links the suite in
the browser; no transpile step, no generated tree. The artifacts import
only wasi 0.2 and test-context, so the stock upstream worker serves the
leg unmodified; this repo's frame is asset wiring, target config, and
results writing (driver-ct/deltic/run-browser.mjs, its own npm tree —
no jco dependency). fetch-translator.ts grows an --asset selector for
the embedder bundle. Matrix: 11 targets, deltic-browser rows identical
to jco-browser case for case.

Co-dependent: the component-test pin moves to b402686 (the deltic
worker ships there), whose repo went jco-free and deleted the
component-test-jco-transpile bin — the thin wrapper is vendored into
driver-ct/jco/ (it resolves this repo's own pinned jco-transpile, and
it is deleted with the jco tree when that leg retires).

Gates: just check; conformance-ct::all with CONFORMANCE_BROWSER=1
(70 results, 0 failing), matrix-check green. Leg wall times on this
box: jco-browser 2.4s, deltic-browser 2.7s.
@lann
lann enabled auto-merge August 10, 2026 17:51
@lann
lann merged commit b174c56 into main Aug 10, 2026
4 checks passed
@lann
lann deleted the deltic-browser branch August 10, 2026 17:52
lann added a commit that referenced this pull request Aug 10, 2026
jco support/coverage is retiring family-wide, retained only in
polymorph-webcrypto (operator ruling recorded on lann/deltic#14). The
deltic rows cover both former postures — stock Deno (deltic-deno*) and
headless Chromium (deltic-browser*, #39) — so the four jco targets come
out: conformance/driver-ct/jco/, their targets.toml blocks, the
justfile recipes and aggregate/pins wiring, the CI Node step and jco
js-lock, and the .gitignore entries. matrix.md regenerated for the
surviving seven targets (42 results, 0 failing).

Also, while touching those lines: the CI publish action's results list
gains the deltic-browser rows it missed in #39 (the local aggregate
recipe already passed them — the same completion #38 made for the deno
rows), and conformance/README's targets table gains the same rows.

Gates: gha::rust-checks, gha::smoke, CONFORMANCE_BROWSER=1
gha::conformance-checks (7 targets / 42 results / 0 failing),
gha::interop — all green locally. The post-gate touch-up was the
CI-yaml results list only (not locally executable).
lann added a commit that referenced this pull request Aug 10, 2026
…ostures"

This reverts commit 677daac (PR #40,
reverse of 8b16928): the jco legs return until the perf comparison
against the deltic legs has been run (operator call, 2026-08-10 —
lann/deltic#17 is the tracking issue; the family ruling that jco
support ultimately remains only in polymorph-webcrypto stands,
lann/deltic#14).

The two #39 wiring completions that rode PR #40 (the publish action's
deltic-browser results rows, conformance/README's deltic-browser table
rows) are re-applied in the follow-up commit rather than lost with the
revert.
lann added a commit that referenced this pull request Aug 10, 2026
The publish action's results list keeps the deltic-browser rows and
the setup action's js-locks gains deltic's lockfile (both missing
since #39 — the local justfile wiring already had them), and
conformance/README's targets table keeps its deltic-browser rows.
Content-identical to what PR #40 carried alongside the removal.
lann added a commit that referenced this pull request Aug 10, 2026
The deltic rows have run green beside the jco rows since #36/#39, on
stock engines (Deno; Chromium via the upstream page driver) with no
transpile step and no JSPI flag. With deltic now the family's JS host,
the jco driver tree, its fork pin, and the jco-node/jco-browser targets
retire; the standing matrix is wasmtime + deltic-deno + deltic-browser
over both signer postures (jco-era matrix history stays in git).

Node 24 stays in CI: the deltic browser driver runs under it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant