Point the build-arg docs at the real API domain, mcp.nearle.ai.in

The API deployed to mcp.nearle.ai.in rather than mcp.catalogue.nearle.ai.in.
This matters more here than on the backend: VITE_API_BASE_URL is inlined at
build time, so a bundle built from the old value calls a host that does not
exist and every request fails with nothing in the server logs.

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

.env.example

@@ -8,7 +8,7 @@
 # production the React app is served from catalogue.nearle.ai.in and the API
 # lives on its own subdomain, so the deployed build needs:
 #
-#   VITE_API_BASE_URL=https://mcp.catalogue.nearle.ai.in
+#   VITE_API_BASE_URL=https://mcp.nearle.ai.in
 #
 # No trailing slash - src/api/client.js concatenates paths that already start
 # with "/api".
@@ -17,8 +17,8 @@
 # the running container does nothing; it has to be passed to `npm run build`.
 # The Dockerfile exposes it as a build arg for exactly this reason:
 #
-#   docker build --build-arg VITE_API_BASE_URL=https://mcp.catalogue.nearle.ai.in .
+#   docker build --build-arg VITE_API_BASE_URL=https://mcp.nearle.ai.in .
 #
 # Whatever origin you set here must also appear in the backend's
 # API_CORS_ORIGINS, or the browser will block every response.
-# VITE_API_BASE_URL=https://mcp.catalogue.nearle.ai.in
+# VITE_API_BASE_URL=https://mcp.nearle.ai.in

Dockerfile

@@ -13,7 +13,7 @@ COPY . .
 # on the running container has no effect, the value is already baked into the
 # JS bundle.
 #
-#   docker build --build-arg VITE_API_BASE_URL=https://mcp.catalogue.nearle.ai.in .
+#   docker build --build-arg VITE_API_BASE_URL=https://mcp.nearle.ai.in .
 #
 # Left empty by default, which keeps requests relative and same-origin so the
 # nginx /api/* proxy below serves them. Set it when the API is on its own