chatbot

At c2f8235 there are four circular imports, all value (runtime) imports: 1. imports and each of those imports from (e.g. ). 2. imports from ; imports from ; imports from . 3. imports from ; imports from . 4. imports and ; and import from . None is a bug on its own but since this is a template, apps built from this version start with them. Mentioning in case you want to untangle them (for example, moving and into modules the others import rather than the other way round). To reproduce: lists them.

Problem The current helper manually constructs UUID v4 values using Modern JavaScript runtimes provide a native Web Crypto API method, , which generates cryptographically secure UUID v4 values. The custom implementation is therefore unnecessary and provides weaker randomness than the native API. Solution Replace the custom implementation with the native API while keeping the existing helper and its current call sites unchanged. This keeps the existing abstraction in place while delegating UUID generation to the platform-provided cryptographically secure implementation.

Summary only called , so the next request still loaded DB history into model context and a refresh restored the old UI. Persist clear by deleting messages (plus related votes/streams) for the current , keeping the same chat. Optimistic UI + SWR cache update stay aligned with DB. already rebuilds context from DB messages, so no route change is required once history is deleted (chosen over starting a new chat id as the smaller product behavior). Test plan [ ] Send a memorable fact in a chat, run , confirm the UI is empty [ ] Ask a follow-up in the same chat and confirm the model does not use the cleared fact [ ] Refresh and confirm cleared messages do not return [ ] Run (mocks DELETE ) Closes #1549