a07370abd0
Addresses review feedback on #73363. The previous truthy `profile_adapters.get(name)` check fell back to the shared (default-profile) adapters whenever a secondary profile's adapter map was empty — which is the normal state before that profile's bot connects (the map is created empty and filled only on a successful connection). That reintroduced wrong-bot cross-delivery for the secondary until it connected. Thread the default profile identity and reserve the shared `adapters` set for it alone; every other profile uses its own adapter map, or an empty set when its bot has not connected yet (so it simply does not deliver that tick). Add regression coverage for the default, connected-secondary, empty-secondary and missing-secondary adapter-map cases.