release: deltic-embedder.mjs — the consumer bundle artifact (Phase 3 enabler) - #34
Merged
Merged
Conversation
…enabler) One platform-neutral ES module (tools/release-bundle/entry.ts) carrying the whole consumer surface: embedder API + Translator + @deltic/ct-runner (runSuite, Context, import analysis, tags inventory — now re-exported from ct-runner's mod.ts as public surface) + wasiShims. Emitted with the browser lanes' own mechanism (deno bundle --platform browser); per the #8 rescope nothing in the graph generates code at run time. Gate (core matrix + AGENTS list): tools/release-bundle/bundle_test.ts builds the artifact exactly as release.yml does, asserts no node:/npm: residues, then drives the example suite through the bundle alone — translate, instantiate, execute, tag-gate (nothing tree-shaken). Also verified by hand under plain Node 24, zero flags: identical counts (callback ABI needs no JSPI) — the premise for polymorph-test's PR-lane selftest in the migration's Phase 3 (#14). release.yml: setup-deno, build the bundle, ship it in SHA256SUMS and the asset list; notes updated.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Phase 3 of the polymorph-test migration (#14) needs deltic consumable by browser workers and plain Node without a Deno toolchain. This ships the embedder bundle as a release asset:
tools/release-bundle/entry.ts: embedder API +Translator+@deltic/ct-runner(incl. the ct-runner: no tag/missing feature-gating (cases N/A per target run and fail) #25 tags inventory, now on ct-runner's public surface) +wasiShims— all existing public API, nothing new; no runtime codegen anywhere in the graph (P1: emitted specialized-JS host-boundary executor (AOT-shaped, no eval) #8 invariant).build.ts:deno bundle --platform browser(same emission as the browser lanes).bundle_test.ts(wired into the core matrix + AGENTS gate list): builds the artifact release-identically, asserts platform purity of the EMISSION (nonode:/npm:residues), and drives the example suite end to end through the bundle alone, tag-gating included.release.yml: deno setup + bundle build +SHA256SUMS+ asset.Verified by hand under plain Node 24 (no flags): identical counts + envelope — the callback ABI needs no JSPI, so polymorph-test's PR lane can gate the browser-leg code path under their existing Node toolchain. 319 KB artifact.
Next (polymorph-test side, after this releases): the deltic browser worker + harness await-tolerance + Node selftest, pinned to the first release carrying this asset.