Repository navigation
Prepare Android alpha20 keyboard and privacy hardening - #61
Merged
Merged
Conversation
added 7 commits
September 19, 2026 20:51
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.
Goal
Ship a bounded Android alpha20 preview with the frozen, locally verified keyboard hardening and presentation work. This is not completion of the full A–M redesign.
Scope
Constraints and non-goals
No telemetry, runtime network permission, ambient capture, passive typing collection, clipboard inspection/history, model-identity changes or preference migration. Explicit Copy recovery does not introduce automatic clipboard writes. No full G recovery controller, replacement Tools composition, language expansion, stable release or unobserved physical-device/accessibility claims.
Verification
The exact frozen product/test source passed on the owned API 35 x86_64 emulator:
Commands:
Local debug SHA-256:
46fe66dd5b34c7c1b8488d84d313d8a7059e255c4a7a05fe822fee683a65e5f5.Local unsigned release SHA-256:
26e7e9296728e71ad6cafea17f95b02ee9653445137190bb0f89ab6d788af4c0.The first full run was 233/234 with a diagnosed IME-selection fixture race. Its failure/source/logcat remain archived; stable setup/restore and failure-preserving Activity cleanup were reviewed before the passing 236-case run. A passing PR fast path does not substitute for full main/manual release CI. Local APKs are not the protected release input.
Release acceptance and stop
See
docs/plans/active/android-alpha20-release-readiness.mdfor the complete contract and evidence. After required checks/review, merge, run full CI at the exact main SHA, then tagandroid-v0.1.0-alpha20. Use only that CI run's unsigned artifact for protected signing, signed upgrade/reinstall checks and prerelease publication (latest=false). Release promotion is authorized; signing/publication also requires confirmation of the independently protected offline signing-key backup. Do not expose key material.Stop feature editing at the frozen candidate. Preserve explicit limits: owned-emulator evidence is not phone comfort, real Obtainium, named-third-party, TalkBack/Switch Access or final A–M acceptance. Cross-editor dictation recovery and the full Tools/accessibility redesign remain planned.