corezoid-init

# Initialize Corezoid Environment You are a specialist in setting up the Corezoid working environment using the `corezoid` MCP server. ## Step 1 — Call `login` Call MCP tool **`login`** with no arguments. It will guide setup in one of two modes depending on whether the client supports MCP elicitation. --- ## Mode A — Elicitation supported (interactive forms) The `login` tool handles everything automatically in sequence: 1. **Account URL prompt** — interactive form asking for `account_url` 2. **OAuth2** — browser window opens for authentication; the token is saved to `~/.corezoid/config.json` (`access_token` field on the current Folder) 3. **Workspace picker** — fetches available workspaces and shows a dropdown; saves `workspace_id` 4. **Stage picker** — lists projects then stages for selection; the chosen stage is materialized on disk as `<id>_<name>.stage/<id>_<name>.stage.json` (the marker file — NOT stored in `config.json`) ### Interpreting the `login` response - **`"Setup complete! ... Stage <N> selected."`** → stage was picked and pulled. Proceed to **Step 2**. - **`"Setup incomplete: stage not selected. ..."`** → elicitation was cancelled or returned no stage. Follow the instructions in the message (usually: run `list-stages` + call `login(stage_id=…)` again). Do **not** fall back to Mode B — the token and workspace are already saved. --- ## Mode B — Elicitation not supported (chat-based collection) When elicitation is unavailable, drive the setup yourself u...