feat: store named device slots independently - #764
Merged
Merged
Conversation
janicduplessis
force-pushed
the
feat/device-slot-registry
branch
from
September 12, 2026 16:55
6088d0d to
6d0f68c
Compare
janicduplessis
marked this pull request as ready for review
September 13, 2026 01:08
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.
Description
A workspace currently has one owned device record per platform. Multi-device support needs independently addressable assignments before launch commands can accept the approved
--slotselector.Solution
Add named-slot registry storage and slot-aware assignment, removal, and Android console-port reservation. Existing
platformsrecords remain the default slot, so existing device claims need no rewrite. Slot names are validated before writes, and removing the last device in a named slot removes the empty slot.This is the storage layer of the multi-device stack. Launch commands do not expose named slots yet; lifecycle enumeration and runtime integration follow in dependent PRs.
Fixes #761.
Test plan
Registry tests exercise 20 same-model assignments, independent slot removal and port release, preservation of default devices, and rejection of unsafe names without changing the registry. These state transitions are the validation for this internal layer; no native tool invocation changes.