polyengine 0.5.0; @polymorph/websocket 0.5.0 - #60
Merged
Merged
Conversation
Adopt the A22 protocol/runtime split: the published host module depends on @polyengine/protocol alone (jsr:@polyengine/protocol@^0.2.2). websocket.ts's vocabulary imports (ComponentException, brand predicates, STREAM, Stream/StreamSource types) move to @polyengine/protocol, which is where they live as of runtime 0.5.0 — the embedder's A9 courtesy re-exports are gone. Application legs bump the five lockstep pins to 0.5.0 and exact-pin @polyengine/protocol@0.2.2; the demo's isComponentException import moves to protocol; browser-bundle-entry re-exports protocol alongside the embedder so bundle consumers keep seeing vocabulary off one namespace. exam-polyengine learns the two-line world: one resolved runtime-family version, one resolved protocol version, and js/polyengine names no @polyengine/runtime specifier. Gates: polyengine-module-check (deno check + 14 tests), exam-polyengine, driver deno task check, conformance run-polyengine (55/55). The WPT parity recipe fails identically on pre-migration HEAD (pre-existing groups-manifest resolution issue, unrelated); its polyengine carrier bundle step succeeds under the new pins.
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.
Adopt the A22 protocol/runtime split: the published host module depends
on @polyengine/protocol alone (jsr:@polyengine/protocol@^0.2.2).
websocket.ts's vocabulary imports (ComponentException, brand
predicates, STREAM, Stream/StreamSource types) move to
@polyengine/protocol, which is where they live as of runtime 0.5.0 —
the embedder's A9 courtesy re-exports are gone.
Application legs bump the five lockstep pins to 0.5.0 and exact-pin
@polyengine/protocol@0.2.2; the demo's isComponentException import
moves to protocol; browser-bundle-entry re-exports protocol alongside
the embedder so bundle consumers keep seeing vocabulary off one
namespace.
exam-polyengine learns the two-line world: one resolved runtime-family
version, one resolved protocol version, and js/polyengine names no
@polyengine/runtime specifier.
Gates: polyengine-module-check (deno check + 14 tests), exam-polyengine,
driver deno task check, conformance run-polyengine (55/55). The WPT
parity recipe fails identically on pre-migration HEAD (pre-existing
groups-manifest resolution issue, unrelated); its polyengine carrier
bundle step succeeds under the new pins.