The chatelet module hardcoded "/chatelet" in its route paths while the
standalone also mounts under a Vite base path ("/chatelet/"), which the
router applies too. The two stacked, so in-app URLs came out
double-prefixed ("/chatelet/chatelet/<id>") and the clean single-prefix
URL ("/chatelet/<id>" — what a person would type or share) matched nothing
and fell back to the room list.
Click-through and refresh already worked on the double-prefixed URL via the
standalone SPA fallback (server-deploy d5f5a19); this is about the URLs
themselves. Make the routes root-relative ("/" list, "/:id" detail,
"/my-bookings") so the base path supplies the single prefix: in-app nav now
produces clean "/chatelet/<id>" URLs, and that shareable form resolves to
the room.
Drop the now-redundant "/" -> "/chatelet" redirect, point the
list/detail/browse links and the Rooms tab at the new paths, and key the
tab's active state off the route name (a "/" prefix test would match
everything).
Verified on a production build served under "/chatelet/" like nginx: the
list, a deep link to a room, a refresh on it, and in-app room clicks all
resolve to the detail page with a single-prefixed URL. vue-tsc build passes.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
