Repository navigation
Host lease side: allocator contract trim, Simlock adapter, coordinator/journal, renewal, recovery #3269
Closed as not planned
Description
Part of #3264. ADR 0021 §4, §7, §8.
This lists the lease-side work so the front-end issues can point at it. The lease-side owner writes the actual contracts, so it is not a full spec.
Scope
- Trim the managed-device allocator contract (
packages/contracts/src/managed-device-allocation.ts) to the amended ADR. RemovesupersedeLeaseRequest,confirmLeaseActivation,getManagedIdentityStatus,acknowledgeManagedIdentityRemovalandactivation: 'external-fence', with their consumers, tests and the Android reuse docs. - A Simlock adapter over Simlock's supported typed client (
simlock/client) on the local Unix socket, failing before mutation on a protocol mismatch. - A coordinator and journal: the durable request and lease mapping, a requester that survives restarts, the idempotency key, and conservative publication.
- Renewal that covers the command deadline plus teardown, coalesced per lease, fencing work when a renewal fails or is uncertain.
- Restart recovery that reconciles outstanding journal entries through Simlock.
- Implement the
HostShapeAllocatorseam from Host: request devices by shape (--device "iPhone 16" / "Pixel 7") #3267, wire it into the daemon runtime withfeatures: ['device-shape']on daemon health, and read the trusted principal from Host: strip client identity, hand the principal to the daemon over loopback, enforce the public route policy #3266. The proposal is in the comments on Host: remote verification through Simlock-backed fresh devices (ADR 0021) #3264. - Keep raw UDID and serial selectors inside the Host lease binding (§5).
Dependencies
callstackincubator/simlock#70 (typed client, durable requests, owned roots).
Activity
feat(host): request devices by shape
feat(host): request devices by shape
feat(host): request devices by shape
thymikee commentedon Oct 7, 2026
Sequencing update: we are integrating Simlock first and deferring the remote Host implementation of ADR 0021. See the decision on #3264.
The core Simlock integration remains the priority: use the supported typed client and establish allocation, automation, teardown/release, renewal, and recovery through the existing managed runtime. Let that working integration determine the required contracts.
The Host-specific parts of this issue—implementing the proposed HostShapeAllocator, consuming the proposed principal handoff, and advertising Host device-shape support—are deferred with #3265–#3268 and PRs #3271–#3274. Those proposals are not prerequisites or settled interfaces for the core integration. Revisit this issue’s Host-specific scope once the integration is working.
Leaving this issue off the on-hold list for that reason; this does not mark its current mixed scope as ready for unattended implementation.
thymikee commentedon Oct 12, 2026
Closing as superseded by the October 10 replacement of ADR 0021 and merged #3372. Agents now acquire, renew and release leases through Simlock themselves; agent-device drives those devices through its ordinary local runtimes. The in-process Host allocator integration was withdrawn.
The October 7 instruction to continue the core typed-client integration is superseded too. The replacement design explicitly has no agent-device Simlock client, allocation journal, managed runtime owner, renewal coordinator or Host lease mapping; #3372 removed those unused foundations.