Implement spec 057 manifest execution modes#578
Merged
Conversation
6fa20bf to
6f04d99
Compare
6f04d99 to
6456317
Compare
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
Implements the first spec 057 slice for app bundle validation: component manifests now support explicit
execution_modevalues forwasmandcompatible, andtraverse-cli app validatereports execution-mode metadata without requiring compatible components to declare WASM artifacts.Governing Spec
057-embeddable-runtime-host044-application-bundle-manifest004-spec-alignment-gate028-schema-alignment-gate-v02031-supply-chain-hardening040-contractual-enforcement-gateProject Item
What Changed
execution_modetowasm, validates WASM and compatible component field requirements separately, and exposes optional WASM artifact metadata for compatible components.execution_moderemain valid.Validation
scripts/ci/spec_alignment_check.shrequires a PR body file and is expected to run in CI against this body.cargo test -p traverse-registry --test application_manifest.cargo test -p traverse-registry -p traverse-cli.bash scripts/ci/embedder_conformance/reference_cli.shbash scripts/ci/downstream_app_bundle_registration_smoke.shcargo clippy -p traverse-registry -p traverse-cli -- -D warningsNotes
This PR adds
scripts/ci/embedder_conformance/reference_cli.shas the initial checked-in conformance entry point. Full platform embedder implementations remain downstream work for the reference-apps platform tickets.