fix(host-service): a terminal in a cloud workspace knows it is in one
Found running the cloud path end to end: in a fresh box superset auth whoami says "Not logged in".
The CLI treats a cloud workspace as its own auth source — it holds no credential, and the firewall adds one naming the workspace — but it detects that from SUPERSET_SANDBOX_WORKSPACE_ID, which host-service sets for itself and never passed to terminals.
Sandbox terminals carry it now. It also gives an agent the id of the box it is working in, which it otherwise has to be told.
Verified in a box on the new golden: superset is on PATH (1.29.0), Node reaches GitHub (200), .env is provisioned; this was the one remaining failure.
https://claude.ai/code/session_01FK6rLzBEUiHHXZWNmpQ2BP
Summary by cubic
Fixes auth in cloud sandbox terminals so superset auth whoami no longer reports "Not logged in."
The CLI authenticates as the workspace in cloud boxes but relied on SUPERSET_SANDBOX_WORKSPACE_ID, which host-service set for itself but never passed to terminals. Sandbox terminals now receive it, which also gives agents the id of the box they're working in.
Summary by CodeRabbit
- Bug Fixes
- Sandbox terminal sessions now retain the associated workspace context, improving consistency when running commands within a sandbox environment.