[tikinang]

The orchestrator serves only the API now, and the web console lives in the Zerops Box app at box.zerops.io. The Box docs still described the console at the root of the workspace's API URL with an API key sign-in.

What changes

• access: the "Web console" section is rewritten for the Zerops Box app: Zerops login only, one organization at a time, Workspaces, the per-workspace console and Team, the three ways to open a console, the project access it takes, and that a workspace stored with zbox workspace use --api-key has no console. The API key sign-in, its session cookie, the one-time sign-in link and the HTTPS caution are gone. Key rotation and the token rules no longer mention a console signed in with the key.
• overview, workspace-service: port 8080 serves the API only.
• getting-started: new "In the Zerops Box app" way to create a workspace. zbox setup --cpu gives shared cores unless --cpu-mode dedicated (zbox v0.5.0), and --organization picks the organization.
• workspace-service: start, stop, restart, reload and resize are also in the Zerops Box app and in zbox workspace (zbox v0.5.0).
• workspace-settings: the console's "Workspace" page is "Settings".
• isolation, faq: wording follows the above.

Verified

On a dev environment with zbox v0.5.0: the API root answers a JSON 404, zbox workspace console prints the Box URL, a URL-and-key workspace is refused a console, key rotation (old key until the reload, an older access refused afterwards, the CLI exits 6 until zbox workspace authorize), stop, start, restart of a sandbox from memory, and resize.

Not verified in a browser on that environment: the New workspace form, the workspace menu and the Settings page were checked against the app's source only.