Point the console at the port the backend actually listens on

apiBase and wsBase defaulted to localhost:3001; continuum-backend
listens on 3000 when PORT is unset, in both src/index.ts and its
.env.example. Starting both with no configuration therefore produced a
console whose every request was refused by a port with nothing behind
it - which presents as a broken API rather than a wrong address.

apps/web/nuxt.config.ts

@@ -21,8 +21,14 @@ export default defineNuxtConfig({
 
   runtimeConfig: {
     public: {
-      apiBase: process.env.NUXT_PUBLIC_API_BASE || "http://localhost:3001",
-      wsBase: process.env.NUXT_PUBLIC_WS_BASE || "ws://localhost:3001",
+      // 3000, which is what continuum-backend listens on when PORT is unset
+      // (src/index.ts, and its .env.example). These defaulted to 3001, so a
+      // developer who started both with no configuration got a console that
+      // could not reach its own backend - every request refused by a port
+      // with nothing behind it, which reads like a broken API rather than a
+      // wrong address. Keep these in step with that default.
+      apiBase: process.env.NUXT_PUBLIC_API_BASE || "http://localhost:3000",
+      wsBase: process.env.NUXT_PUBLIC_WS_BASE || "ws://localhost:3000",
       // There is deliberately no go2rtcStreamBase here any more. A camera
       // stream lives on a gateway inside a particular farm's network, each
       // farm has its own, and the gateway tells the backend its address when