Repository navigation
Select joint SC2 current guest and browser source completion - #4633
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.
Amend the existing shared WASM plan to select one current-only SC2 S1 completion and S2 browser/source migration in existing SC2 PR #44. The earlier isolated-S1 prohibition on production entrypoint, recording and qualification-source edits is explicitly replaced. The source amendment was provided to the SC2 owner before remote delivery, so documentation merge is not a development gate.
The selected composition retains the maintained stateful guest family and all five real URL variants; genuine current selection/canonical configuration and SC6G ACK at every actual caller; one awaited installed browser runtime; and connected build, custody, recording and offline assertions. Preserve strict validation, domain authority, lifecycle/failure controls and existing qualification budgets. Native S2, SC2C-01.6f, product acceptance/publication, whole WASM and .7 remain open.
Reconcile the accepted supplier prerequisite: immutable published Game producer
6732d237, qualifier20c94478, successful fresh both-feed installed 39023332496/a1 and protected-main 39023124943/a1, recorded by merged Game #717. Retain original 39016307973 and 39020851715 failures and original 0.3 history. Narrow only the WASM open-index row; reconcile the descriptive registry/compatibility profile to this exact audited P/Q join, preserving published 0.4 identity and excluding arbitrary qualifiers. Capture the decision and supplier boundary in public Atlas with generated seed/manifest closure.Validation: native run/merge reads, owning/shared Atlas retrieval and immutable citation checks, full inert Atlas delivery (18 tests; 223 records; 352 local citations), maintained registry preparation check, added-link/scope assertions and git diff --check. Independent exact source/registry/Atlas review passed
4cdcf804ed9f1fedafcc83798cca3009bfe5ff06; full required hosted CI follows. No local CLR/native/browser workload or SC2 implementation change is part of this PR.architecture-map: unaffected; owning scope and accepted frontier only