feat: worktree-isolated network identity (own ip/port/domain) + hosts crash fix

[graphicfox]

4.3.0 — worktree apps run side by side with main

Fixes the bug report: a worktree app couldn't start because only the compose project name was namespaced — the loopback IP / host port / hosts domain still came from .env, so the worktree reused main's APP_IP and the container failed to bind (:443 already allocated). It also depended on rewriting .env, which dirties a committed .env and fails when .env is read-only.

What changed

• New AppIdentity overlay. The effective compose project / domain / IP is now resolved at runtime and injected into docker compose (shell env overrides .env), the loopback alias, and the hosts entry — never written to .env.
  • Inside a worktree: suffixed compose project + derived domain + its own stable loopback IP (allocated once, cached in the per-worktree registry). → runs alongside main on its own ip/port/domain.
  • .env and .env.template stay untouched → works even when .env is committed or read-only, and git status stays clean.
  • main checkout unaffected; Doppler project stays shared.
• lab up --domain <domain> / --ip <ip> to set the identity explicitly (CI/agents).
• Fix: DockerHosts.removeDomain/removeCurrent crashed with "Could not iterate given object!" (passed a Map to the vendored forEach). Now use native Map.forEach — also fixes lab down's hosts cleanup.

Not needed anymore

The reporter's manual workaround (hand-editing APP_DOMAIN in the worktree .env) is obsolete. (lab test -y for headless runs already shipped in 4.1.0.)

Verification

npm run build ✅ · npm test ✅ (29 suites / 59 tests). New AppIdentity tests (main passthrough, worktree isolation, fresh-IP allocation + idempotent reuse, suffix idempotency, overrides) and a DockerHosts regression test (no Map-iteration crash). The docker-level side-by-side run is validated by the reporter's environment.

🤖 Generated with Claude Code