Repository navigation
feat(android): apply authenticated RVD1 budgets to RVT1 clients - #306
Merged
Merged
Conversation
This was referenced Oct 22, 2026
The Android slice changed companion behavior; AGENTS.md requires the plan's evidence to move with it.
turinglambdaai
marked this pull request as ready for review
October 22, 2026 15:38
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.
Scope
createDeviceRVT1Clientas the explicit post-RVD1 construction boundary; consume accepted per-session payload/pending limits, never an untrusted discovery value.Validation
Kotlin tests and the full GitHub matrix are queued on this PR; not claimed green until the checks complete. This is a framework handoff/budget slice, not device pairing, credential storage, or mobile packaging.
Base:
1248a90cdf347edfb44731ff7c8f69c94df96d59.