feat(runtime): Component Model WIT host-capability activation - #1355
Merged
Conversation
Validate exact Traverse WIT imports through explicit application activation so Host ABI v1 stays unchanged. Co-authored-by: Cursor <cursoragent@cursor.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
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.
Summary
component-wit-v1activation path that validates exacttraverse:platformWIT imports and resolves them only through application-activated target-local bindings.core-wasm-v1fixtures unchanged; Callweavecallweave:recording/recording-hostis not an automatic alias.recording-host@0.1.0for status/start/stop/events, fail-closed selection, domain outcomes, and redacted evidence.Closes #1341
Governing Spec
135-component-model-wit-host-capabilities004-spec-alignment-gate065-sigstore-bundle-verificationProject Item
What Changed
traverse_runtime::component_witmodule; Host ABI v1 whitelist and executor path are unchanged.core-wasm-v1packages keep the same load path.Validation
cargo test -p traverse-runtime --lib component_witcargo clippy -p traverse-runtime --lib -- -D warningscargo check -p traverse-runtime --target wasm32-unknown-unknown --no-default-features(CI 1.94.0 toolchain)component_wit.rsline coverage 100% (runtime gate 100%)scripts/ci/local_preflight.sh --pr-body)Made with Cursor