Port Spawn onto the shared chat block #5
Description
Summary
Use Spawn as the second consumer to validate richer product requirements.
Related repo: https://github.com/Sarai-Chinwag/spawn
Goals
- adapt sessions, gateway transport, and availability states to the shared model
- keep billing, provisioning, and account logic in Spawn
- confirm the shared block can support a more productized chat experience cleanly
Done when
- Spawn-specific business logic remains in Spawn
- shared UI stays generic
- adapter seams are proven by a second real integration