fix(console): re-enable MSW in Vercel build so record detail URLs resolve on demo.objectui.org

Agent-Logs-Url: https://github.com/objectstack-ai/objectui/sessions/1c5f4098-f5a5-40fc-a9ae-1c55c5c66f6d

Co-authored-by: xuyushun441-sys <255036401+xuyushun441-sys@users.noreply.github.com>

Author: Copilot

CHANGELOG.md

@@ -7,6 +7,26 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+### Fixed
+
+- **"Record not found" on the Vercel demo (`demo.objectui.org`).** The
+  Vercel build previously set `VITE_USE_MOCK_SERVER=false` in
+  `apps/console/vercel.json`, which caused the deployed console to
+  forward every `/api/v1/*` call to an external ObjectStack backend via
+  `VITE_SERVER_URL`. The example apps (`crm_enterprise`, `todo`,
+  `kitchen_sink`) are shipped as MSW seed data, not as data in that
+  remote backend, so clicking a record navigated to
+  `/apps/.../record/<composite-id>` and `findOne()` returned null —
+  `DetailView` then rendered its *Record not found* empty state. The
+  Vercel build is now aligned with the existing `build:vercel` script
+  in `apps/console/package.json` and sets `VITE_USE_MOCK_SERVER=true`,
+  so the deployed demo is fully self-contained: MSW boots the
+  in-memory ObjectStack kernel with the example apps' seed data,
+  records persist in `localStorage` across reloads, and record detail
+  URLs resolve against the same kernel that served the list.
+  `apps/console/README.md` now documents the self-contained demo mode
+  and the optional "point at a real backend" override.
+
 ### Changed
 
 - **`MetadataProvider` now lazy-loads metadata.** Previously the console

apps/console/README.md

@@ -60,19 +60,29 @@ Both modes support the same features and use the same codebase. Choose developme
 
 ## Vercel Deployment
 
-The console can be deployed as a standalone static SPA (e.g. to Vercel) that connects to a remote ObjectStack backend. The build configured in `vercel.json` disables the MSW mock worker (`VITE_USE_MOCK_SERVER=false`) so that all `/api/v1/*` requests go to the real backend.
+The console is deployed to Vercel (e.g. `demo.objectui.org`) as a **self-contained static SPA** — the MSW mock worker runs in the browser and serves all `/api/v1/*` requests from an in-memory ObjectStack kernel with persistent localStorage storage. No external backend is required.
 
-**Required environment variable** (set in the Vercel project's *Environment Variables* panel):
+The build configured in `vercel.json` enables the MSW mock worker (`VITE_USE_MOCK_SERVER=true`) so that:
+
+- Seed data for the example apps (`crm_enterprise`, `todo`, `kitchen_sink`) is loaded on first visit.
+- Records, views, and user-created data persist in `localStorage` across page refreshes.
+- Record IDs (including composite driver-assigned IDs such as `crm__account-<timestamp>-<n>`) remain stable per-browser, so record detail URLs keep working after reload.
+
+No environment variables are required for the standalone demo deployment.
+
+### Optional: pointing at a real backend
+
+If you want to deploy the console against a live ObjectStack backend instead of the self-contained demo, override the build command to set `VITE_USE_MOCK_SERVER=false` and set `VITE_SERVER_URL` in the Vercel project settings:
 
 | Variable | Example | Description |
 | --- | --- | --- |
-| `VITE_SERVER_URL` | `https://demo.objectstack.ai` | Absolute URL of the ObjectStack backend. When unset, requests default to the same origin — which will 404 on a static SPA host. |
+| `VITE_SERVER_URL` | `https://your-backend.example.com` | Absolute URL of the ObjectStack backend. When unset, requests default to the same origin — which will 404 on a static SPA host like Vercel. |
 
 Additional backend requirements for cross-origin deployments:
 
 1. The backend must allow CORS from the SPA origin (`Access-Control-Allow-Origin: <spa-origin>`, `Access-Control-Allow-Credentials: true`).
 2. Auth cookies must use `SameSite=None; Secure` so they are sent on cross-site requests.
-3. The apps and objects referenced in URLs (e.g. `crm_enterprise`, `lead`) must actually exist in the backend metadata — otherwise the console will render its *object not found* empty state.
+3. The apps and objects referenced in URLs (e.g. `crm_enterprise`, `lead`) must exist in the backend metadata and expose stable record IDs — otherwise the console will render its *object not found* / *record not found* empty state.
 
 ## ObjectStack Spec Compliance
 

apps/console/vercel.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://openapi.vercel.sh/vercel.json",
   "installCommand": "cd ../.. && pnpm install --frozen-lockfile",
-  "buildCommand": "pnpm msw:init && NODE_OPTIONS=--max-old-space-size=4096 VITE_USE_MOCK_SERVER=false VITE_BASE_PATH=/ vite build",
+  "buildCommand": "pnpm msw:init && NODE_OPTIONS=--max-old-space-size=4096 VITE_USE_MOCK_SERVER=true VITE_BASE_PATH=/ vite build",
   "outputDirectory": "dist",
   "framework": "vite",
   "rewrites": [