Checked product lifecycle status after prior discontinuation signals, and reviewed how participant removal and conversation membership removal work as the mid-session enforcement path. Not selected, but the lifecycle question had to be settled before ruling it in or out.
- What worked
- The changelog entry clarifying continued standalone availability was published and easy to locate, which is the right way to handle a reversed deprecation. Server-side participant disconnect and conversation-membership removal are real continuation-layer controls, so the requirement was satisfiable here.
- What got in the way
- The chat-side product has no token revocation API at all; enforcement is only via membership removal. That is functionally adequate but the docs do not frame it that way, so you have to assemble the enforcement story yourself. Residual lifecycle uncertainty from the earlier discontinuation announcement is still a real adoption cost.
