Repository navigation
Conversation
…s codegen/closure-semantic.mjs
…s codegen/closure-semantic.test.mjs
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
1 participant
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.
Hardens #172 with exact cross-language semantic vector: explicitly specifies locale-independent UTF-16 code-unit tuple order (astral U+10000 before BMP U+E000), replaces the old placeholder
hex-closure.jsonchecksum with its computed SHA-2562f704cfa7c9f59894d97d4b2552e7dec0e6bdee6852a70b1dca8cd50b9e78684, publishes the exact 1550-byte JCS preimage invalidation/package-security/golden/hex-closure.canonical-preimage.json, and adds Node regression tests for reversed dependencies, duplicate tuple, root repetition, Unicode ordering and resolver/lock digest drift. The non-ASCII reordered vector is pinned as SHA-25684efe3277da20763fbc5134d9568390493d6b4f7faffd02e4f47e66302af68a4.These semantic witnesses are not a third shape authority: independently authored TypeSpec/JSON Schema and TJSV remain authoritative. Downstream Rust/Dart/TS exact-byte verification and CI exact-head confirmation are required before merge; draft.