Repository navigation
Add isolated Android JNI DPS quality fixture with consent lifecycle - #10
Merged
Merged
Conversation
…ion-20261022 Distinguish reviewed IPv6 configuration from live reference counts
…eline-20261022 Retain strict IPv6 baseline diagnostics for native DPS
…on-20261022 Distinguish completed emulator configuration checkpoints
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.
Add a synthetic Android debug Activity and JNI bridge to the pinned shared Core DPS input-quality implementation. Explicit consent and lifecycle checks reject late, revoked, expired and background results. The fixture preserves the existing Organic Maps integration boundary and does not claim main-navigation or sensor support.
The disposable hosted harness verifies pinned acquisition and offline rebuilding, process-scoped KVM access, loopback-only runtime, cancellation and owned cleanup. The integrated #12/#13/#14 stack distinguishes completed-emulator configuration checkpoints from raw operational metadata, retains both results, and refuses unknown renderer families before acquisition. Quiet, failed and cancelled controls keep strict comparison.
Validation: source revision 1546bf3 passed source run 39844211892 (124 checks) and Components 39844211893 (31 checks). Original actual trial 39844370003 passed all eight named Android/JNI cases, two cancellation controls with six tracked processes extinct each, group-reaping controls and owned state removal. Artifact 12454922115 (100,955 bytes) independently matches API SHA-256 234b28aa81eca4ea68a9148845096b7a132f1976b5fbe547c24172ff7ce57a65. Aggregate independent review found no blocker for this bounded fixture. Integrated retained head 0f473e8 has the exact tested tree 714e806a71325ffab27e5b16e4e785305b73557b; current required Components checks remain a separate merge gate.
The actual runner used Linux 7.0.0-1017-azure; Linux 6.17 runtime is untested. IPv6 raw fingerprints match, firewall differences are counters-only and KVM timestamps changed. The completed-emulator configuration result is true while the raw aggregate remains false. Earlier failures remain failed under their original criteria and are retained in docs/DPS_INTEGRATION.md and the original artifacts.
Physical positioning, sensors, main Map navigation, authenticated OS app identity, confidential execution, JNI-specific Android sanitizer coverage, transient host effects and complete kernel-resource absence remain unverified. This PR accepts the synthetic debug/JNI slice only.