docs: record physical Play install-order evidence - #551
Closed
daniele21 wants to merge 4 commits into
Closed
Conversation
Owner
Author
|
/preflight auto |
Owner
Author
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.
Records the successful physical Google Play Internal Testing smoke evidence for the current Harnex/RedactGuard integration, including the actual Play App Signing identities reported for the installed builds.
Confirmed on representative Android hardware with Play-delivered builds:
PENDINGActual Play App Signing SHA-256 digest reported for both applications:
D6:2D:3C:C8:51:D5:72:05:C3:42:C1:7F:86:26:40:58:E3:FE:29:6A:AE:1B:0E:43:FD:AC:58:82:24:44:1A:BDBecause the two Play-delivered applications currently share the same App Signing identity, this physical run closes install-order / authorization / connectivity / real-inference evidence for the current Play topology, but it does not prove the distinct-Play-signer topology required for a physical independent-signer claim under ADR 0018. Independent-signer behavior remains covered by deterministic cross-app automation.
This PR intentionally does not mark broader Harness 0.5 SR-6, JNI/GGUF, memory, thermal or representative-device release evidence as complete.