zerg-ship

# Zerg Ship Cycle ## Surfaces - **Public demo runtime** — `https://longhouse.ai` — Coolify app `longhouse-demo` - **Control plane** — `https://control.longhouse.ai` — private repo/service; public deploys only health-check it - **Hosted tenant runtime** — `https://<subdomain>.longhouse.ai` — reprovisioned runtime container managed by the control plane `longhouse.ai` is a demo-mode Longhouse runtime, not a static landing page. ## Ship Types Do not blur these lanes: - **Hosted deploy** — updates public Longhouse runtime surfaces running on the hosted runtime host: public demo runtime and hosted tenant runtimes. The hosted control plane is an external private service for this public repo; runtime deploys may check it, but do not ship it. - **CLI/package release** — updates the user-installed `longhouse` CLI from the GitHub release wheel used by `scripts/install.sh`. Existing users do not get this from a hosted deploy. They need a new install or upgrade: `uv tool upgrade longhouse` or rerun the installer. - **Runner release** — updates the separately installed runner binary/service. This is its own release/update path and is not covered by the normal runtime or control-plane deploy lanes. If a change touches `longhouse claude`, local hook install, local launcher behavior, `connect --install`, or other code that runs on the user's machine, do not say "deployed" as if hosted users now have it. That kind of change needs a CLI/package release, and sometimes user...