Files
Ignacy Łątka adb600c14c fix(tool-server): say a booted device was passed over, instead of "boot one"
The zero-candidate refusal read "No booted device runs `poke` ... Boot one" for
a pool where a device IS booted and was dropped by the capability filter. Taking
that advice boots a second device, and every later device-less call is then
ambiguous — a transient wrong-platform pool turned into a permanent one. The
`ios-remote` arm already had a note for the same confusion; this is the other,
far more common, reason to pass a booted device over.

Also replaces the `advertisedSchema` guard's test, which was vacuous in the file
as it runs: an earlier test's `createRegistry()` has already written
`inputSchema` onto every module-level singleton, so the helper returned that and
never reached the registration the `{ ...def }` copy exists to protect. Built
from a pristine definition, it fails alone and in the suite.
2026-09-02 15:37:36 +02:00
..