portless-dev-setuplisted

# Skill: portless-dev-setup Adopts [portless](https://portless.sh) for stable, git-worktree-aware `.localhost` dev URLs, following its **documented** best practices — not a hand-rolled approach — then wires it into [Conductor](https://conductor.build) so every workspace gets its own URL with no port threading. portless replaces a dev server's port with a stable URL and is git-worktree-aware: in a linked worktree it auto-derives `https://<worktree>.<project>.localhost`. Run this when asked to "set up portless", get stable dev URLs that survive across git worktrees, refactor a brittle hand-rolled port/host wrapper, or make a repo safe for several Conductor agents running the frontend in parallel. Work in **phases** and report findings before any large change. The scope boundary is the whole point: portless wraps **exactly one** thing — a JS/TS HTTP dev server. Everything else (backends, databases, Docker/compose, brokers, fixed non-HTTP ports) needs a *different* isolation strategy, covered in Phase 3. ## Ground rules - **Verify against the live docs and the installed CLI — do not trust memory.** Run `portless --help` and `npm view portless version` before pinning anything, and `WebFetch` the portless / Conductor docs before recommending config. - **Pin dependency versions exactly**, matching this repo's existing convention — check whether other deps use exact vs `^`/`~` and match it (this repo's `package-json-style` rule prefers exact). - **Smallest change that follows th