Host integration: use Simlock as the local device allocator

[thymikee]

Purpose

agent-device Host will use a local Simlock daemon to supply managed devices.

Host owns network access, user identity, sessions, automation, artifacts, and supervision. Simlock owns device allocation, capacity, lifecycle, health, and cleanup.

Host uses the Simlock Unix socket. Simlock does not need a new public network API.

ADR 0021 defines this boundary.

Required work

• Export a supported typed client for the local daemon #71: Export a supported typed client for the local daemon.
• Make lease requests durable across restart #72: Store lease requests so that clients can recover them after a restart.
• Put managed iOS simulators in an owned device set #73: Put managed iOS simulators in an owned device set.
• Write provisioning intent before a driver creates a device #74: Store provisioning intent before a driver creates a device.
• Create a new iOS simulator for each lease #75: Create a new iOS simulator identity for each lease.
• Add configured warm targets and convergence status #76: Add small, configured warm targets.
• Add durable maintenance prepare and resume operations #77: Add a durable maintenance mode.
• Add durable admin-only component preparation #78: Add durable admin-only component preparation.

Platform rules

• iOS creates a new simulator identity for each Host lease. Simlock deletes the simulator after release, expiry, or recovery-driven lease termination.
• Android can reuse an emulator identity. Simlock must check the clean state after Host installs an execution fence.
• Host keeps the managed execution claim for an Android identity during its full pool lifetime, including idle and reclaim states. Host clears the claim only after Simlock proves that the identity was removed.

Related work

• Install missing platform components on demand (iOS runtimes, Android system images, extensible profile sources) #67 and feat: on-demand component installation for iOS runtimes and Android system images #69 provide the platform installers that Add durable admin-only component preparation #78 uses. The local-first Host slice can use components that are already installed. Host must not let an ordinary lease request enable a download.
• HTTP API: expose the simlock control plane over the network #65 and feat(http): expose the control plane over HTTP #68 add an optional HTTP interface. Host does not use this interface.
• agent-device integration: bind the HTTP control plane into agent-device as a remote lease provider #66 uses Simlock as a network provider. Host uses Simlock as a local allocator instead.

Completion conditions

• One local connection can control concurrent leases up to the configured capacity.
• A retry or process restart cannot create a duplicate lease.
• Simlock is the only owner of capacity and managed-device lifecycle.
• Simlock rejects an incompatible client before a mutation starts.
• Maintenance stays active after a restart.
• Cleanup cannot change a foreign device.
• A reusable Android identity cannot become unclaimed between leases or during reclaim.