Interactive cloud startup wires up device signing, but the slot for tools served back is empty.
A slot for serving tools back to a remote session is wired in but hardcoded empty in this build.
What's wrong with this entry?
Starting an interactive remote or teleport session now also passes a served-settings-change callback into device registration and threads the resulting held call into the session config, plus an event signer once a device id is known. The slot for tools served back to the remote session is present but hardcoded to nothing, so it is never populated in this build.
deviceHooksProcessMemories
Strings lifted out of the shipped bundle, so the claim above can be checked against them.