c0d8d6b5d5
Under gateway.multiplex_profiles a secondary profile with Twilio / LINE / Teams / BlueBubbles / Microsoft Graph / WhatsApp Cloud / WeCom-callback / Feishu-webhook credentials was refused WHOLE at config load (SecondaryPortBindingConfigError): every one of its platforms was skipped because these adapters bind their own port and the default profile owns the one listener. The refusal is gone. gateway/platforms/shared_ingress.py gives port-binding adapters a shared-listener mode: the runner stamps `_shared_listener_profile` on a secondary's port-binder, `bind_listener()` publishes the adapter's fully wired aiohttp app instead of starting a TCPSite, and the default listener (api_server, or the webhook adapter when there is no api_server) forwards `/p/<profile>/<tail>` to the served profile's adapter whose router matches `/<tail>`, under that profile's runtime scope. The request is therefore verified by the NAMED profile's adapter with its own secret and replies leave through that adapter; the un-prefixed path keeps serving the default byte for byte; an unknown profile or a profile without an adapter for the path is a 404, never another profile's bot. api_server and webhook stay MIRRORS (the default's own adapter answers /p/<profile>/ for them) and are the only port-binders a secondary must not enable; `SHARED_LISTENER_MIRROR_PLATFORMS` is that set in gateway/config.py. The adapter records its public callback URL (`ingress_url`) in gateway_state.json under `<profile>:<platform>` and logs it once at connect, so the operator knows what to paste into the vendor console.