Repository navigation
Retain closed initial policy closure failure diagnostics - #30
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 retained Count1 attempt refused before browser startup and recorded only
initial-closure:exception, leaving its inner cause unknown. Initial closure failures now retain a bounded, closed subcheckpoint and code, including unexpected exceptions; the capture parser and failure projection preserve that detail. Existing closure, custody and digest checks still fail closed, original exceptions are reraised, and noninitial diagnostic bytes are unchanged. Raw exception text and private material are never emitted.Validation: locked Release build and the full runtime-evidence source gate pass, including genuine missing/hash/JSON/custody/argv controls, closed parser/projection and legacy-frame checks, 38 Quint scenarios, 500 invariant samples, complete-state/effect correspondence and 13 rejected mutants. Local verification used the official private SDK/Core and an explicit exact-commit SourceLink input because the local clone has no canonical remote metadata; canonical hosted qualification remains required.
The owning roadmap records this source evidence. The old native attempt remains refused with its exact cause unknown, useful play remains 0/6, and changed policy bytes require a protected successor build and a distinct future operation grant.