Repository navigation
Keep administrator mobile pairing usable across cache and token limits - #83
Merged
Merged
Conversation
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.
Administrator pairing could succeed while the phone remained read only: a valid conversation history exceeded the 256 KiB cache budget, and access expiry stopped the app after 15 minutes without automatic renewal. Connection settings also offered no route into the operational tabs after pairing.
Keep the full live history and cache contiguous recent history within the existing byte limit, fetching a fresh history page when a cached conversation has no retained events. Renew expired credentials on the active timer, startup, and foreground return, preserving generation fences and never replaying commands. Keep cached views accessible during renewal and add Open Automonique to paired settings. Prepare Android preview.11 with version code 10.
Validation: complete npm run validate passed, including 559 tests, typecheck, lint, security/native policy, doctor, all-platform exports, and production bundle checks. A private live administrator diagnostic loaded 79 conversations and 3,778 events, reproduced the cache failure, then verified bounded cache admission, read-only offline reopening, a live resumed projection, and credential rotation. Diagnostic credentials were revoked. Exact Android artifact acceptance and publication follow the protected-main preview workflow.