Repository navigation
docs(#1823): record Decision 129 for the Rust embedder's compatible lifecycle - #1827
Merged
Merged
Conversation
…ifecycle Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
Summary
Records Decision 129 from the #1823 brainstorm: the Rust
traverse-embeddergets the compatible lifecycle by sharingruntime.wasm's rules.traverse-runtime-wasminto a pure module intraverse-contracts. Both crates already depend on it, and it already holds the Spec 1722 helpers.runtime.wasmandtraverse-embedderboth call that module, so there is still one copy of the rules and no Wasm engine in the embedder.runtime.wasmbehaves the same but is re-pinned.TraverseEmbedderApi::start_compatibletakes raw JSON text (&str), so all four canonical-input rejection vectors behave the same as on the other hosts. This is breaking, which is allowed before 1.0.submitgets the same rule in Rust traverse-embedder submit takes raw JSON text (Decision 129) #1826.Docs only.
Governing Spec
072-native-bridge-compatible-lifecycle057-embeddable-runtime-host1722-canonical-guest-input-bytesProject Item
Refs #1823 (Project 1, Ready). The decision is the first step; implementation follows under the same issue.
Validation
scripts/ci/spec_alignment_check.shandscripts/ci/pr_body_check.shpass locally🤖 Generated with Claude Code