arketix 0.1.1 → 0.3.0

package/README.md

@@ -1,6 +1,6 @@
 # arketix
 
-The command line of the Arketix control room (https://crm.admin.acredix.cl), for founders and agents. Its commands come from the CRM's operations, so a new operation is a new command with no new release.
+The command line of Arketix ERP (https://erp.arketix.cl), for founders and agents. Its commands come from Arketix ERP's operations, so a new operation is a new command with no new release.
 
 ```sh
 npm i -g arketix
@@ -11,12 +11,14 @@ arketix crm companies get --rut 76.123.456-0 --json
 arketix crm activities log <companyId> --type call --date 2026-10-22 --summary "Llamada con operaciones"
 arketix crm contacts remove <contactId> --confirm
 arketix call crm.opportunities.update @input.json
+arketix --org personal finance summary --currency GBP
 arketix help crm opportunities
 ```
 
 - **Flags come from each operation's input.** `ownerId` is `--owner-id`, enums are choices, objects and arrays take JSON, `--input '<json>'` passes the whole input. An operation with exactly one required id also takes it as one trailing word.
 - **Output.** People get a table for a list and `key: value` lines otherwise. `--json` prints one line: the output, or `{"error":{"code","message","retryable"}}`.
-- **Sign-in.** `login` keeps the token in the OS keychain. `ARKETIX_TOKEN` overrides it. `--env prod` (default) or `local` (http://localhost:3417); `ARKETIX_URL` points anywhere else.
-- **Catalogue.** Every command, and help for one, asks the CRM for its list of operations. The list is cached per server version and CLI release in `~/.cache/arketix`, which only saves the `tools/list` call while the CRM's version is unchanged. Nothing falls back to it: when the CRM can't be reached or gives no usable answer, the command exits 9, and a refused token exits with its code. `arketix`, `arketix help` and the built-ins' help need no token and no connection, so they list only the built-ins; `arketix help crm` lists the CRM's commands.
+- **Sign-in.** `login` keeps the token in the OS keychain. `ARKETIX_TOKEN` overrides it. `--env prod` (default, https://erp.arketix.cl) or `local` (http://localhost:3417); `ARKETIX_URL` points anywhere else. A token kept by 0.1.x for https://crm.admin.acredix.cl still signs in to prod; `logout` forgets both.
+- **Workspaces.** A person may belong to several workspaces (organizations). `--org <slug>` makes every request of this run act in that one, `ARKETIX_ORG` when the flag is absent; it is per run, so jobs running side by side never move each other. Without either, a call acts in the workspace you last chose (the sidebar, or `arketix account workspace switch --slug <slug>`, which an agent member cannot run), else your first. `arketix whoami` names it; `arketix account me` lists them all. A workspace you don't belong to exits 10.
+- **Catalogue.** Every command, and help for one, asks Arketix ERP for its list of operations. The list is cached per server version and CLI release in `~/.cache/arketix`, which only saves the `tools/list` call while the server's version is unchanged. Nothing falls back to it: when the server can't be reached or gives no usable answer, the command exits 9, and a refused token exits with its code. `arketix`, `arketix help` and the built-ins' help need no token and no connection, so they list only the built-ins; `arketix help crm` lists the CRM module's commands.
 
-Exit codes: 0 ok, 1 other CRM error, 2 usage, 3 unauthenticated, 4 read-only token, 6 confirmation required, 7 not in catalogue, 8 rate limited, 9 connection lost (a write may have run), 10 forbidden, 12 input invalid.
+Exit codes: 0 ok, 1 other error, 2 usage, 3 unauthenticated, 4 read-only token, 6 confirmation required, 7 not in catalogue, 8 rate limited, 9 connection lost (a write may have run), 10 forbidden, 12 input invalid.