penguin-harness-manual-test

# Standing PenguinHarness up to test by hand Node >= 24. `dev:*` runs `dev-prebuild.mjs` first (keeps `pnpm install` current, prebuilds workspace deps); `pnpm desktop` runs a full `pnpm -r build`, so it is slow to start. ## Entry points | Command | Open | Data root | | --- | --- | --- | | `pnpm dev` | http://localhost:7365 | `~/.penguin/dev-data` | | `pnpm desktop` | its own window | `~/.penguin/dev-data` | | `pnpm dev:landing` | http://localhost:7366 | none (static) | | `pnpm dev:docs` | http://localhost:7367 | none (static) | Other fixed ports (`packages/core/src/internal/ports.ts`): 7364 installed server, 7368 dev backend, 7369 `pnpm penguin web` (data root `~/.penguin/dev-data-cli` — its own, so it can serve while an Agent it hosts runs `pnpm dev`; the lock is per root). On a shared box, `ss -tln` before assuming one is free; `PORT=` inline moves it. The user's installed app, server and CLI all use `~/.penguin/data` — their real Agents, Sessions and keys. Never point a dev run there. Both surfaces print the root they took (`Data root: …`, `[shell] dev instance … on data root …`); read it rather than assume. ## Four ways a working setup looks broken **7368 shows a stale app.** The dev backend also serves `packages/web/dist` — the last `pnpm -r build`, not what Vite is serving. Screenshot 7365, never 7368. **`curl` returns 502 but the server is fine.** A shell `http_proxy` routes loopback through the proxy. Use `curl --noproxy '*'`. Browsers and the server itself ar...