@wave-ai-os/wave-cli 0.1.87 → 0.2.0

package/README.md

@@ -88,7 +88,6 @@ Optional env:
 - `WAVE_AGENT_NAME`
 - `WAVE_AGENT_RUN_ID`
 - `WAVE_REQUEST_ID`
-- `WAVE_CONFIG_PATH`
 - `WAVE_TIMEOUT_MS`
 - `WAVE_DEBUG`
 - `WAVE_OPENAPI_PATH` (local contract file, e.g. `openapi/wave-cli.yaml`)
@@ -100,7 +99,7 @@ Deterministic precedence:
 - 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)
+- config file (`--config` or `~/.wave/config.json` when present)
 - production API default (`https://api.ourwave.io`)
 
 Config files are JSON objects using the same keys accepted by `--auth-json-stdin`, for example:
@@ -165,7 +164,7 @@ wave doctor --readable
 
 Namespace taxonomy:
 
-- Primary: `osmd`, `broadcast`, `support`, `recognition`, `whiteboards`, `time-tracking`, `planner`, `tasks`, `projects`, `rocks`, `meetings`, `members`, `teams`, `issues`, `foundation`
+- Primary: `osmd`, `broadcast`, `support`, `recognition`, `whiteboards`, `time-tracking`, `planner`, `tasks`, `projects`, `goals`, `meetings`, `members`, `teams`, `issues`, `foundation`
 - Advanced: generated CRUD resources, `markdown-tree`, content/meta/resource-specific command groups
 - Aliases / shortcuts: `find`, `open`, `ls`, `cat`, `tree`, `phantom` help alias
 
@@ -218,7 +217,7 @@ wave tasks update --id 99 --status in_progress
 wave tasks destroy --id 99
 wave projects list
 wave projects show --id 123
-wave rocks update-status --id 55 --status on_track
+wave goals update-status --id 55 --status on_track
 wave meetings show --id 77
 wave members show --id 44
 wave members meta-profile --member-id 44 --json
@@ -280,9 +279,8 @@ wave open "Ted Martinez"
 wave ls --path "directory/Members/Ted Martinez"
 wave cat --path "directory/Members/Ted Martinez/Member Profile"
 wave tree --path "knowledge/Processes" --depth 2
-wave pulse update --id 12 --data-json '{"status":"on_track"}'
 wave subtasks list --task-id 123 --page 1 --per 20
-wave milestones list --rock-id 234 --page 1 --per 20
+wave milestones list --goal-id 234 --page 1 --per 20
 wave subitems list --list-item-id 345 --page 1 --per 20
 wave subtodos list --todo-id 456 --page 1 --per 20
 wave subissues list --issue-id 567 --page 1 --per 20
@@ -303,11 +301,11 @@ These child resources enforce parent IDs at CLI validation time:
 - `list-items.create` requires `list_id`
 - `issues.create` requires `issue_group_id`
 - `todos.create` requires `todo_group_id`
-- `rocks.create` requires `rock_collection_id`
+- `goals.create` requires `goal_collection_id`
 - `kpis.create` requires `smart_kpi_view_id`
 - `scorecards.create` requires `measurable_group_id`
 - `subtasks.create` requires `task_id`
-- `milestones.create` requires `rock_id`
+- `milestones.create` requires `goal_id`
 - `subitems.create` requires `list_item_id`
 - `subtodos.create` requires `todo_id`
 - `subissues.create` requires `issue_id`
@@ -384,12 +382,6 @@ wave knowledge list --focus-member-id 67 --page 1 --per 50
 - `questions.list` supports only `asked` and `answered` filters (plus `page` / `per`).
 - `questions.list` does not expose `--query-json`; unsupported filters are rejected at CLI parse time.
 
-`pulse.create` contract notes:
-
-- Requires `health_update.health_updatable_id`, `health_update.health_updatable_type`, `health_update.member_id`, and `health_update.status`.
-- Legacy `updatable_id`/`updatable_type` are normalized to `health_updatable_id`/`health_updatable_type`.
-- `health_update.status` must be `on_track`, `at_risk`, or `off_track`.
-
 `surveys.create/update` contract notes:
 
 - Use `survey.name` and `survey.recipient_type` (`title` is normalized to `name`).
@@ -407,12 +399,6 @@ wave knowledge list --focus-member-id 67 --page 1 --per 50
   - `manager_review`
   - `onboarding`
 
-`feedbacks.create/update` contract notes:
-
-- Use `feedback.name` (`title` is normalized to `name`).
-- `feedbacks.create` requires `feedback.name`, `feedback.quarter`, `feedback.year`.
-- `feedback.quarter` must be `q1`, `q2`, `q3`, or `q4`.
-
 `accountability.create/update` contract notes:
 
 - Use `responsibility.name` (`summary` is normalized to `name`).