embabel up

Start the appliance and complete first-run setup. Safe to run at any time — a running mode is reconciled with the compose file rather than started twice, and a completed setup says so instead of asking again.

Flag
--worlds	the world runtime and its console
--me	the personal-assistant door
--fresh	delete all data first (asks), then start over

With neither flag it starts the mode this machine is already running, or was last set up as — recorded as EMBABEL_MODE in .env the first time. Without that record, embabel down then embabel up handed an assistant user a world runtime on the same graph and said nothing about it. The installer now opens the Worlds door too, which narrows the gap without closing it: EMBABEL_MODE=me ... | sh installs an assistant, and this has to come back to one. Worlds is the fallback for a machine that has set up neither.

The first run pulls roughly 0.8 GB before handing the terminal back, then continues downloading the rest — the code sandbox, metrics, and structured document conversion — behind you. embabel status says what is still arriving.