Repository navigation
Add private UNQUALIFIED Android recovery harness - #53
Merged
Merged
Conversation
ictechgy
marked this pull request as ready for review
October 29, 2026 14:22
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.
Scope: draft source qualification only
Validation
Independent exact-source review passed. Host recovery 81 and lease 4 checks passed; G0 55, package 17, native contracts 311, capture 64, runtime resources 26 and CLI 33 passed. Exact source was restored from its verified bundle and 81 contracts rerun successfully. Actual helper compilation and three native/JVM tests remain pending CI; local JDK 17 was unavailable.
Explicit limits
Runtime remains UNQUALIFIED and T18 is not complete. No ordinary recovery API or persistent availability change, no automatic retry of uncertain input, no knownStart/replay/fixture promotion. No actual Android process, gesture, Binder, screenshot or app qualification. Future disposable-device testing and any production integration need separate authorization and review.
The existing helper startup bearer token can remain in private files/live-config.json until overwritten by later startup; this does not erase that residue. Recovery journals never store or reload that token, and restart cannot resume native effects. Failure may retain private output/live owners rather than claim disposal.
Public tool code and synthetic tests only. This PR is for draft publication and CI, not ready/merge, device runtime, company inputs, key generation or deployment.