[Bug Report] Multiple regressions: Font rendering asset failure, broken keyword search, and generation timeouts

Describe the bug

Over the past week, Chatbot Arena has encountered several critical UI/UX and functional regressions that heavily impact usability. These bugs persist across Windows 11 Pro on multiple browsers (Chrome, Edge, Firefox) including Incognito mode, confirming it is a server-side/CDN issue and not a local client cache problem.

Steps to reproduce & Details

1. Font Rendering Asset Failure (UI Regression):

   • Symptom: The custom fonts fail to render, falling back to a raw, un-aliased system sans-serif font (as shown in the attached screenshot).
   • Technical note: Checking the browser's inspect tool shows that the font-family CSS rules are defined correctly, but the actual font assets are not loading or displaying. This points to a broken CDN link, expired SSL/CORS policies for assets, or missing font files on the host server.

2. Broken Chat History Search:

   • Symptom: The search bar in the sidebar now strictly filters chats by their generated title.
   • Previous behavior: It used to perform a full-text keyword search across the entire conversation body, displaying a list of all chats containing that specific word.

3. Infinite Generation & Timeout Errors:

   • Symptom: Models generate text indefinitely, eventually crashing with a response error.
   • Example Trace ID: f387b61df2b7d396ce546f9e50929ed8

4. Broken Discord Invite:

   • Symptom: The Discord community links on the website are currently invalid or expired, blocking new users from joining.

Expected behavior

• Web fonts should load correctly from the CDN/server assets.
• Chat search should scan conversation contents, not just titles.
• Stable text generation without constant Trace ID timeouts.
• Updated, working Discord invite link.

Additional context

Tested on Windows 11 Pro across all major browsers. The issue is persistent and global.
(Attached screenshot demonstrating the font fallback issue)

No files, tests, or entry points are identified, and the report combines font assets, chat search, generation timeouts, and the Discord invite. Start by reproducing each regression and locating the separate UI, search, generation, and link owners; done means each listed expected behavior is restored and verified across the reported browsers.