Repository navigation
Retain installed Fable dependency proof with exact package provenance - #716
Merged
Merged
Conversation
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.
Fresh both-feed qualification reached 32 general browser tests and Rust2/C4 checks on each feed, then refused ordinary Fable dependency source/support files during evidence projection. Both selected supervisor suites were unreached; both diagnostic uploads are retained as ineligible evidence from original run 39020851715/attempt1.
Classify finite Fable module/context roles across the general consumer, selected compiler output/browser copy and restored Worker trees. Copied package sources and library runtime bytes join their original package members; generated JavaScript and transformed projects join their original inputs. Consumer archive merge admits only its own contexts. Unknown members, unsafe paths, links and provenance drift still refuse, and mandatory Core/lock/Worker proof and existing caps remain required.
Validation: independent exact source review; clean static workflow preflight and 14 inert collector controls passed. Complete current coherent CI is required. Published 0.4 producer 6732 and all package/model/trace/tool/semantic harness inputs remain unchanged; no installed retry or publication is selected by this PR.
Owning scope: WASM-SHARED-01/.5-P2→S1 in docs/roadmaps/wasm-shared-01.md and the existing shared foundation plan. This is the same outcome-led-programme-20261016 campaign and wasm-terminal-process-20261017 dependency chain.