I shipped a feature in May. Cross-page session memory for a retrieval agent — follow a link, the conversation comes with you. It was deployed, tested, and running in production.
Yesterday I found out no visitor had ever been able to reach it.
The part that was actually broken
The obvious problem was that the chat widget existed on exactly one page out of thirty-nine. That is bad, but it is the kind of bad you notice.
The real problem was underneath. The widget never sent a session_id field. Or a scope field. The server had both, documented, tested, deployed — and the browser had simply never been wired to send either one.
