Repository navigation
Build a closed Worker successor with bounded startup observations - #719
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.
The generated Worker policy currently loads an ESM dependency graph before the mechanical command handler becomes available. Prepare coherent unpublished
0.5.0with one closed ESM Worker built from the actual generated F# policy and mechanical entry. Exact locked build-only tools compare two builds of captured input buffers, check the delivered module closure and retain raw policy, source, lock and final-byte custody. Published0.4.0and its accepted P/Q evidence remain immutable.Add optional bounded scalar readiness/admission/SHA/native-instantiation observations without routing advisory packets into the lifecycle reducer or renewing the pre-create deadline. Actual transport identity, clock, timer, capacity and termination rules remain. Prepared installed tests exercise fresh initial and abort-to-new physical Workers, cold expiry, and a genuinely compiled message withheld beyond expiry then released as an explicitly injected delivery impairment. No earlier timeout cause is inferred.
Validation:
7d10c1b475c54e098c702c2738c0ef276ea0aa4d; root reviewed changed safeguards. Review corrected alias escapes in the closure guard and joined the Worker build tree to the outer custody tree before execution.Owning outcome: Game718, existing WASM-SHARED-01 plan. Owning Atlas
game/closed-worker-build-boundarycaptures source and remaining gates without private consumer evidence. This source PR does not publish or install0.5.0, accept product/native outcomes, or launch an image operation. Future publication and finite installed binding require genuine successor P/readback.The first qualifier 39069862111/a1 failed static preflight before compiler or runtime qualification: Lifecycle.Tests retained one Project-type Contracts range at 0.4.0. The repair changes that project metadata edge to 0.5.0, preserves every external package hash and historical lock, and makes the existing stale-range mutant use the actual immediately previous baseline. The actual extracted preflight passes; all 24 lockfiles and six Wasm ProjectReferences were swept. Independent exact repair/capture review passed
b99aa1560ac3da2edc4b4c5f44482856f10fecf8; the original failure is retained and fresh full qualification remains required.