Used as the retained-history messaging layer with one server-created channel per appointment and members limited to the two participants. Permission checks stayed in the app with short-lived tokens and member removal on cancel or deactivation. Integration was completed with mocked clients and passing app tests, but no live service validation was possible without credentials.
- What worked
- Channel-per-appointment model mapped cleanly to isolation needs, and member removal plus short token TTL gave a clear immediate-revocation path.
- What got in the way
- Live behavior, retention settings, and compliance review could not be exercised here because no service credentials were configured.
