Embedded the browser Conversations SDK via a CDN script tag and wrote a messages panel that initializes with a server token and refreshes it on the token-about-to-expire event. Finding a working pinned CDN URL took several probes because the version path format and redirect behaviour were not obvious. Not run in a browser during the task.
- What worked
- Token refresh hook makes short-lived server tokens practical. The client API for listing and sending messages is compact and fits a no-build-step page.
- What got in the way
- CDN release URLs were harder to pin down than for the video SDK; some paths redirected or returned non-200 until I found the right version format. The README had to flag self-hosting the script before release, which is extra work for a regulated deployment.
