@wave-ai-os/wave-cli 0.1.62 → 0.1.65

package/README.md

@@ -1,4 +1,4 @@
-# @wave/cli
+# @wave-ai-os/wave-cli
 
 Machine-first CLI used by a Node LangGraph agent to execute semantic Wave operations against the Rails API.
 
@@ -19,7 +19,7 @@ See also:
 ## Install
 
 ```bash
-npm install @wave/cli
+npm install @wave-ai-os/wave-cli
 ```
 
 Or run locally from source:
@@ -39,7 +39,7 @@ Secure stdin auth/context examples:
 ```bash
 printf '%s' "token-value" | wave --token-stdin --base-url https://api.example.com --organization-id 42 tasks list --page 1 --per 10
 
-printf '%s' '{"token":"token-value","baseUrl":"https://api.example.com","organizationId":"42","agentName":"atlas"}' \
+printf '%s' '{"token":"token-value","baseUrl":"https://api.example.com","agentName":"atlas"}' \
   | wave --auth-json-stdin tasks list --page 1 --per 10
 ```
 
@@ -66,11 +66,13 @@ Notes:
 
 ## Runtime Contract
 
-Required (from flags, stdin, or env):
+Required (from flags, stdin, env, config, or stored credentials):
 
 - `WAVE_API_TOKEN`
 - `WAVE_API_BASE_URL`
-- `WAVE_ORGANIZATION_ID`
+
+Organization-scoped data commands use the organization certified by the
+authenticated CLI token. `--organization-id` is the only local override.
 
 Optional env:
 
@@ -86,7 +88,7 @@ Optional env:
 
 Deterministic precedence:
 
-- explicit flags (`--token` / `--jwt`, `--base-url`, `--organization-id`, and tracing/runtime flags)
+- explicit flags (`--token`, `--base-url`, `--organization-id`, and tracing/runtime flags)
 - stdin context (`--token-stdin` or `--auth-json-stdin`)
 - env vars (`WAVE_*`)
 - config file (`--config`, `WAVE_CONFIG_PATH`, or `~/.wave/config.json` when present)
@@ -98,7 +100,6 @@ Config files are JSON objects using the same keys accepted by `--auth-json-stdin
 {
   "token": "token-value",
   "baseUrl": "https://api.example.com",
-  "organizationId": "42",
   "agentName": "atlas"
 }
 ```
@@ -146,7 +147,6 @@ wave time-tracking report --start-date 2026-01-01 --end-date 2026-01-31
 wave planner events --starts-at 2026-01-01T00:00:00Z --ends-at 2026-01-07T00:00:00Z
 wave planner public-booking-link --slug intro-call --starts-at 2026-01-01T00:00:00Z --ends-at 2026-01-07T00:00:00Z --timezone America/Phoenix
 wave api ls
-wave graphql fields
 wave osmd schema
 wave osmd examples
 wave markdown-tree schema
@@ -170,7 +170,7 @@ Examples:
 
 ```bash
 wave tasks list --project-id 123
-wave tasks create --project-id 123 --title "Fix auth bug"
+wave tasks create --project-id 123 --summary "Fix auth bug"
 wave tasks update --id 99 --status in_progress
 wave tasks destroy --id 99
 wave projects list
@@ -231,7 +231,6 @@ wave osmd examples
 wave osmd schema
 wave capabilities list
 wave api ls
-wave graphql fields
 wave doctor
 wave find "Ted"
 wave open "Ted Martinez"
@@ -249,8 +248,10 @@ wave subtasks create --data-json '{"subtask":{"task_id":"123","member_id":"67","
 wave subissues destroy --id 999
 ```
 
-All commands require organization context via `--organization-id` or `WAVE_ORGANIZATION_ID`.
-You can also provide `organizationId` via `--auth-json-stdin`.
+All organization-scoped commands use the authenticated CLI token organization
+by default. Use `--organization-id` only when intentionally targeting a
+specific organization; an explicit mismatched value is sent to the backend and
+its authorization response remains visible.
 
 ## Parent-Child Create Rules