dev-local-setup

# Set up a `dev-local` launcher for this codebase Goal: produce **one script** (`scripts/dev-local.sh`) that a person or agent runs to bring the whole local stack up — every long-lived dev server in its own tmux window, plus any infra (DB, cache, queues) the app needs — and a short skill doc so it's discoverable later. Do NOT start any dev servers yourself. You are *generating* the launcher, not running it. Build it, syntax-check it, then hand it to the user to run. > This is the **local, single-stack** launcher. For **concurrent agents** that each > need their own isolated stack (one laptop can't run N), see `crabbox-setup` — the > cloud counterpart. It reuses this script's service/port discovery, so set this up first. ## Step 1 — Investigate the repo (don't guess) Discover the real facts before writing anything: 1. **Package manager & layout** — look for `pnpm-workspace.yaml` / `turbo.json` / `nx.json` / `lerna.json` (monorepo) or a single `package.json`, `Cargo.toml`, `go.mod`, `pyproject.toml`, `Makefile`, `Procfile`, `docker-compose.yml`. 2. **Services to run** — each app/package with a `dev`/`start`/`serve` script, or each `Procfile` line, or each `docker-compose` service. Note the exact command to start each (e.g. `pnpm --filter <name> run dev`, `npm run dev`, `cargo run`, `uvicorn app:app --reload`). 3. **Ports** — grep configs and `.env` for the port each service binds (`PORT`, `listen(`, `server.port`, framework config like `rsbuild.config`, ...