one default port, and it is 9000

Every PORT fallback in the tree now says 9000. There were three answers to one
question, each defensible where it was written and none of them visible from the
others:

  server.tsx and 19 sidecars   5000    a default from before there was an installer
  user-instance.ts             9010    what scripts/setup-old/setup.sh really wrote
  .env.example                 9000    what we told people to write

5000 goes first because macOS binds it — AirPlay Receiver has owned it since
Monterey, so a dev server there fails to bind or gets shadowed by something that
answers.

All 22 sites moved together, which is the point. Changing the app alone would have
turned a consistent-but-wrong default into a split one: the app on 9000 while
nineteen sidecars still dialled 5000.

9010 was the interesting one. It was the only value that ever matched a real
machine, because it is what the old installer wrote — and it was in the single
file whose disagreement would have broken chat alone, with nothing else looking
wrong. Its own comment records the same bug being fixed once already, within the
file, by a change that left it disagreeing with everything outside it.

Note what these defaults actually are: the sidecars bind nothing. user-instance.ts
has no listener at all — it builds ws:// and http:// URLs that both address the
app's single listener. So every one of these numbers is a guess at where the app
is, for a value that .env always supplies. Worth removing rather than aligning,
which is a separate change.

Not typechecked (empty node_modules, frozen installs). Every edited file parses
under `bun build --no-bundle`; the pm2 profile loads.

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

ecosystem-files/ecosystem.profile.cjs

@@ -69,7 +69,7 @@ function defineProfile({ file, include, excluded }) {
 
   // `cwd` is pinned because Bun auto-loads .env from the working directory (and the pty sidecar does
   // `import 'dotenv/config'`). Without it, starting pm2 from anywhere but the repo root silently falls
-  // back to PORT=5000 with no POSTGRES_URL.
+  // back to the default PORT with no POSTGRES_URL.
   //
   // It also decides where the install is. src/servers/data-path.ts derives OFFICER_ROOT as the PARENT of
   // the working directory, and data/, capabilities/ and dockers/ hang off that — so a wrong cwd does not