Conversation
chore: sync release-closeout main back into dev
Integrate the validated LIA-80 cross-APK Activity persistence and terminal-state evidence into dev.
…y-e2e test: exercise Harnex with release package identity
* docs: redesign public README around product and evidence * docs: make README image placeholders explicit
Align RedactGuard with the repo-template-sw 0.11.0 product-engineering model while preserving RedactGuard-specific Android, privacy, product-UI and current public README guidance.
Owner
Author
|
/preflight full |
Owner
Author
|
/preflight auto |
Owner
Author
|
/preflight full |
Owner
Author
|
/preflight full |
1 similar comment
Owner
Author
|
/preflight full |
daniele21
marked this pull request as ready for review
September 7, 2026 14:58
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
1 participant
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.
Release promotion
Promote the current pre-release
devbaseline to stablemainthrough the repository RELEASE path.Exact candidate
dev@12d20f05654df24a7a57bbf7e1671fed7933772fmain@46fa7597757161e30624552d23cd805ddf0d4523Included state
0.11.0product-engineering baseline plus RedactGuard Android/product-UI customizations;0.1.0-alpha.11;PENDINGand replacement-signerSIGNATURE_CHANGEDsemantics;Physical Play evidence and pre-release interpretation
The actual current Play Internal pair passes the physical first-party journey: RedactGuard-first, Harnex-later without reinstall, fail-closed Host absence,
PENDING, exact authorization, Connect / Disconnect / Reconnect and representative production Consumer SDK/Binder/local-analysis execution.The collected Play App Signing metadata reports the same current SHA-256 digest for Harnex and RedactGuard. The canonical runbook explicitly permits this same-signer first-party topology for the current pre-release stable repository promotion because the topology is recorded truthfully and signing identity is not used as a trust shortcut. Deterministic distinct-signer authorization evidence remains mandatory.
This physical run is not distinct-signer Play qualification. Before the first public release that depends on independently signed application distribution, or before claiming physical distinct-signer Play readiness, repeat the focused Play journey with distinct observed signing identities.
Automated RELEASE/FULL requirement
The documentation-budget fix moved
devto12d20f0.... Merge only after exact-head/base RELEASE/FULL and other required checks are green against livemain.Broader LAS-07 ARM64/JNI/GGUF/resource, memory/thermal/OEM and other claim-specific physical evidence remain separate.