Repository navigation
Preserve finite evidence for ambiguous install output - #238
Merged
Merged
Conversation
Deploying puptime with
|
| Latest commit: |
1973b44
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://9fe1f45b.puptime.pages.dev |
| Branch Preview URL: | https://codex-android-install-ambigu.puptime.pages.dev |
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 signing diagnostic currently reports only
ambiguous-contentwhen bounded install output contains conflicting public markers. Preserve that decline and record its first predicate, fixed count buckets, success-marker boolean, a sorted set drawn only from the existing49 public codes, and an unknown-code boolean. Observed codes never become an acceptedinstallCodewhile ambiguity remains.Unknown getter/proxy/inherited diagnostic objects fail closed. Supported native own-data result classification, the49-code grammar, status/size/path/full-frame gates, install commands, capabilities, assertions and cleanup stay unchanged. Validation: source self-check and adversarial privacy cases;5200 old/new native-result fixtures (4692 ambiguous,392 accepted);642 unchanged command-helper fixtures;9 unchanged-install assertion cases;6 canonical evidence tests; exact source/call/cleanup preservation. Author and root probes used Node26.9; this new source still needs the hosted Node22 inline predevice check. No current install cause/mode, native transition, provider or release acceptance is claimed by this PR.