ui: Remove PWA navigate fallback to prevent caching API endpoint requests

[allozaur]

Removes the navigate fallback setting which caused an unwanted re-routing to index.html after caching it for the llama serve endpoints like /models, /props, /slots etc.

[Copilot]

Pull request overview

This PR updates the SvelteKit PWA configuration for the UI so the service worker does not interfere with llama serve API endpoints (for example /models, /props, /slots, /v1/models) by routing navigations to index.html.

Changes:

• Removes the previously exported PWA_KIT_OPTIONS.NAVIGATE_FALLBACK helper and its usage in devOptions.
• Sets a workbox.navigateFallback override intended to prevent the PWA plugin from adding a navigation fallback route that can affect API endpoints.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[allozaur]

@ServeurpersoCom @aldehir

ready for review & testing

[ServeurpersoCom]

I suspected as much; I merged it to my server right after your push --force, and I didn't encounter any regressions with the direct links (settings / conversations) in Firefox:)
The PWA still needs testing.

[allozaur]

I suspected as much; I merged it to my server right after your push --force, and I didn't encounter any regressions with the direct links (settings / conversations) in Firefox:) The PWA still needs testing.

besides the obvious PWA testing path, what needs to be tested manually is entering the / path and then entering /models or /props for instance. I just tested on ur server and it worked perfectly after clicking the update app alert.

[ServeurpersoCom]

This LGTM, (no address bar to check URL on PWA), quick test OK no problem on install / any pages

[aldehir]

Giving approval, won't be available to test for a couple of days.