Repository navigation
Record accepted synthetic Android JNI checkpoint and remaining DPS scope - #15
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.
Record the original passing run 39844370003, its independently verified artifact and exact tree carried into main by the reviewed PR14/13/12/10 stack. All eight synthetic JNI cases and owned cleanup passed; the completed-emulator configuration comparison passed while the raw aggregate remained false.
Keep earlier failed trials and all sensor, physical-accuracy, main-navigation, app-identity and runtime limits explicit. The actual runner used Linux 7.0; the 6.17 profile was not exercised at runtime. Source code and pins are unchanged. Documentation was checked against the original receipts and independent technical review; whitespace checks pass.