Skip to content

Deltic legs: both composed artifacts runtime-linked on stock Deno - #36

Merged
lann merged 1 commit into
mainfrom
deltic-conformance-leg
Aug 10, 2026
Merged

Deltic legs: both composed artifacts runtime-linked on stock Deno#36
lann merged 1 commit into
mainfrom
deltic-conformance-leg

Conversation

@lann

@lann lann commented Aug 10, 2026

Copy link
Copy Markdown
Collaborator

The polymorph-tls entry in the jco-replacement migration (lann/deltic#14), following the pattern polymorph-websocket#40 established — side by side with the jco targets, nothing jco-side changes.

Two standing targetsdeltic-deno (suite-plain, missing-features = [delegated-signer]) and deltic-deno-delegated (suite-delegated): the composed artifacts runtime-linked under deltic on stock Deno. No transpile, no generated tree, no --experimental-wasm-jspi. No SUT host module (the TLS delivery is fused in-guest) — the whole import surface is wasiShims() + the runner's own test-context.

Notables:

  • Tag scheduling from the artifact itself: deltic reads the suite's embedded component-test:tags@0.1 inventory (survives wac composition), so the per-target N/A sets match the wasmtime legs by construction.
  • Provenance parity: the envelope's artifact-sha256 is re-pointed at the un-composed suite, mirroring the wasmtime legs' --suite-artifact — the aggregate's mixed-hash warning never fires.
  • Pin pre-83fff30: import-map URLs + frozen deno.lock for the module graph, sha-pinned translator release asset, cross-checked at run time (fetch-translator.ts).

Matrix: 9 targets, 56 results, 0 failing; deltic rows identical to the wasmtime/jco rows case for case. Committed matrix.md regenerated (browser legs included via a local CHROME_PATH run). just conformance green end to end, matrix-check included. CI gains a pinned denoland/setup-deno step.

Two standing conformance targets, deltic-deno + deltic-deno-delegated
(conformance/driver-ct/deltic/, the deltic analogue of jco/run-node.mjs
and the pattern polymorph-websocket#40 established): the composed
artifacts run runtime-linked under the release-pinned deltic — no
transpile step, no generated tree, no --experimental-wasm-jspi (async
exports run on the callback ABI under stock Deno). No SUT host module
on this leg (the TLS delivery is fused in-guest); the import surface is
deltic's wasiShims() + its runner-supplied test-context. Tag scheduling
reads the suite's embedded inventory (it survives wac composition;
deltic#25), with --missing mirroring targets.toml per target; results
provenance points at the un-composed suite exactly like the wasmtime
legs' --suite-artifact, so the aggregate's mixed-hash warning never
fires. Pin: pre-83fff30 (deno.json import map + frozen deno.lock;
translator asset sha-pinned by fetch-translator.ts).

Matrix: 9 targets, 56 results, 0 failing — the deltic rows match the
wasmtime/jco rows case for case (plain: 2 N/A + 1 pass in delegated/;
delegated: 1 N/A + 2 pass). CI conformance job gains a pinned deno
setup; matrix regenerated with the two new columns (browser legs run
locally via CHROME_PATH for the refresh). just conformance green end
to end, matrix-check included.
@lann
lann enabled auto-merge August 10, 2026 00:22
@lann
lann merged commit 8e6df42 into main Aug 10, 2026
3 of 4 checks passed
@lann
lann deleted the deltic-conformance-leg branch August 10, 2026 00:23
lann added a commit that referenced this pull request Aug 10, 2026
The #36 miss: the aggregate action enumerates results files in ci.yml
independently of the justfile's aggregate recipe, and the two new
non-optional targets without results entries made its validation fail
loud (correctly) on the post-merge run. Same one-line-per-target fix
polymorph-websocket needed (their #40 second commit).
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