fix(vite): resolve stranded merge conflict markers in vite.config.ts

Merge commit 13ad692 ("merge: forum standalone") committed
vite.config.ts with unresolved <<<<<<< / ||||||| / >>>>>>> markers
in the navigateFallbackDenylist regex array. Vite couldn't parse
the file, so the hub dev server failed to restart on config changes
and kept serving stale code from before the merge — including the
old monolithic main app's /market route, which manifested as a
mysterious redirect from / → /market for users testing the hub.

Resolution: keep the union of all three sides
  (sortir, castle, wallet, chat, market, cart, checkout, tasks,
   forum, submit, submission).

Recovery for anyone seeing the stale /market redirect after pulling:
  - hard-reload the browser (Cmd/Ctrl-Shift-R)
  - DevTools → Application → Service Workers → Unregister
  - Re-run npm run dev (or dev:all) — the hub now restarts cleanly

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

vite.config.ts

@@ -25,13 +25,7 @@ export default defineConfig(({ mode }) => ({
           '**/*.{js,css,html,ico,png,svg}'
         ],
         // Don't intercept standalone app paths — they have their own service workers
-<<<<<<< HEAD
-        navigateFallbackDenylist: [/^\/sortir\//, /^\/castle\//, /^\/wallet\//, /^\/chat\//, /^\/market\//, /^\/cart\//, /^\/checkout\//, /^\/tasks\//],
-||||||| af33801
-        navigateFallbackDenylist: [/^\/sortir\//, /^\/castle\//],
-=======
-        navigateFallbackDenylist: [/^\/sortir\//, /^\/castle\//, /^\/forum\//, /^\/submit\//, /^\/submission\//],
->>>>>>> feat/forum-standalone
+        navigateFallbackDenylist: [/^\/sortir\//, /^\/castle\//, /^\/wallet\//, /^\/chat\//, /^\/market\//, /^\/cart\//, /^\/checkout\//, /^\/tasks\//, /^\/forum\//, /^\/submit\//, /^\/submission\//],
       },
       includeAssets: [
         'favicon.ico',