@zoahhq/cli 0.1.6 → 0.1.8

package/README.md

@@ -41,8 +41,13 @@ Reads always check local first; falls back to global.
 zoah login                                      # global default
 zoah login --local                              # project-specific override
 zoah login --base-url https://zoah.example.com
+zoah login --organization acme                  # skip the organization list
 ```
 
+After you sign in, the CLI asks which organization to work in. Your active organization in the web app is first and selected. Use the arrow keys to choose another, then press Enter. An account with one organization skips the question.
+
+The CLI keeps this choice. Changing organizations in the web app does not change it. New projects from `zoah import` go into this organization. A repo that already has `.zoah/config.json` keeps updating its own project.
+
 The CLI uses `ZOAH_BASE_URL` when it is set. Otherwise, it uses `https://zoah.com`. `OPACITY_BASE_URL` remains a compatibility fallback.
 
 ### `zoah logout`
@@ -56,15 +61,27 @@ To clear both, run logout twice.
 
 ### `zoah whoami`
 
-Prints the active user, the source credentials file, and the base URL. Use this when project credentials hide the global token.
+Prints the active user, the source credentials file, the base URL, and the organization the CLI works in. Use this when project credentials hide the global token.
 
 ```bash
 zoah whoami
 # Signed in as you@example.com (global).
 #   Source:   ~/.zoah/credentials.json
 #   Base URL: https://zoah.com
+#   Organization: Acme (acme)
 ```
 
+### `zoah organization`
+
+```bash
+zoah organization list           # your organizations; * marks the CLI's
+zoah organization switch         # choose from the list with the arrow keys
+zoah organization switch acme    # or name one by slug, name or id
+zoah organization create "Acme"  # create one; switch to it to work there
+```
+
+`switch` changes the organization for the credential it came from, so a `--local` login keeps its own organization. The MCP server uses the same organization unless `connect` names another.
+
 ### `zoah mcp`
 
 Runs the Zoah MCP server over stdio so a coding agent (Claude Code, Codex,
@@ -245,6 +262,9 @@ zoah swap --print-issues warn      # print issue details
 
 The dry-run mode is the safe way to preview what swap will do before letting it touch your source tree.
 
+React wrappers preserve root HTML props and use `elementProps` for supported nested form controls.
+See [native HTML elements](docs/native-elements.md) for the supported tags, examples, and limits.
+
 #### Authenticated installs (`.npmrc` management)
 
 Published packages carry the project's privacy. CLI imports are private by
@@ -252,6 +272,14 @@ default, so the install needs credentials. When the repo's `.npmrc` (and your
 `~/.npmrc`) has no token for the Zoah registry host, swap mints a registry
 API key for the project's organization and manages the file for you:
 
+- A key reads only its own organization's packages. When `.npmrc` already has
+  a key, swap asks the registry whether that key can read this package. If the
+  registry refuses it (401 or 403), for example because the key came from a
+  project in another organization, swap replaces it with a key for this
+  project and says so. `.npmrc` holds one key per registry host, so a repo
+  that installs packages from two organizations needs a key that can read
+  both.
+
 - The key is requested through the authenticated import API, requires write
   access in the project's organization, and is **reused** on repeat runs (one
   key per project + user, not one per invocation). It appears in Project