e4080b381b
The first Bot Mode roster paint after launch ran pullServerAvatars over every row, and for a source-scoped row (every row on a local-primary desktop once host.agents annotates the roster) each profiles.get_asset / set_asset went through requestForBot -> host.requestProfile -> requestGatewayForAgent, i.e. a (connectionId, profile) secondary that spawns that profile's pooled backend. With ~60 registered profiles and 3 warm slots this queued 56 background spawns at boot; each queued dial then rode reconnectSecondary's backoff until the stall budget parked it (#107969), so the pool never drained and desktop.log filled with "waiting for a free local slot" (#102978). The active gateway's own profiles.list already produced these rows by reading every local profile directory; get_asset/set_asset are the same directory reads addressed by name. Route both through host.request on the active socket with the row's backend profile name (route.targetProfile, so managed aliases still resolve). No secondary socket, no pool slot, no spawn. Cross-connection (remoteSource) rows never reached this path: pullServerAvatars is fed activeSourceRoster, which filters them out.