@ted-galago/wave-cli 0.1.6 → 0.1.8

package/README.md

@@ -105,16 +105,16 @@ wave lists create --data-json '{"name":"Weekly List"}'
 wave list-items create --data-json '{"list_id":"123","summary":"Follow up"}'
 wave todos create --data-json '{"todo_group_id":"55","name":"Send update","status":"open"}'
 wave knowledge create --data-json '{"content":{"name":"Runbook","content_type":"process","status":"draft","member_id":"67"}}'
-wave notes create-member --target-member-id 67 --name "1:1 Note" --body "Strong progress"
-wave notes create-manager --actor-member-id 67 --target-member-id 68 --name "Manager Note" --body "Coaching plan"
-wave notes create-team --actor-member-id 67 --team-id 9 --name "Team Note" --body "Team context"
-wave notes create-project --actor-member-id 67 --project-id 80 --name "Project Note" --body "Project context"
-wave notes create-customer --actor-member-id 67 --customer-id 30 --name "Customer Note" --body "Customer context"
-wave notes create-contact --actor-member-id 67 --contact-id 31 --name "Contact Note" --body "Contact context"
-wave notes list --contentable-type Member --contentable-id 67 --member-id 67 --page 1 --per 20
-wave notes show --id 1001
-wave notes update --id 1001 --name "Updated Note" --body "Updated body" --status published
-wave notes destroy --id 1001
+wave content create-member --target-member-id 67 --name "1:1 Note" --body "Strong progress"
+wave content create-manager --actor-member-id 67 --target-member-id 68 --name "Manager Note" --body "Coaching plan"
+wave content create-team --actor-member-id 67 --team-id 9 --name "Team Note" --body "Team context"
+wave content create-project --actor-member-id 67 --project-id 80 --name "Project Note" --body "Project context"
+wave content create-customer --actor-member-id 67 --customer-id 30 --name "Customer Note" --body "Customer context"
+wave content create-contact --actor-member-id 67 --contact-id 31 --name "Contact Note" --body "Contact context"
+wave content list --contentable-type Member --contentable-id 67 --member-id 67 --page 1 --per 20
+wave content show --id 1001
+wave content update --id 1001 --name "Updated Note" --body "Updated body" --status published
+wave content destroy --id 1001
 wave markdown-tree root --tree-view
 wave markdown-tree resolve --tool-key projects --node-key tasks --parent-id 123
 wave markdown-tree children --tool-key directory --node-key members --record-id 67
@@ -201,6 +201,8 @@ If a required parent field is missing, CLI returns JSON error with exit code `2`
 - Use `question.name` (legacy `summary` is normalized to `name`).
 - `questions.create` requires `question.member_id` and `question.name`.
 - `question.status`, when provided, must be `asked` or `answered`.
+- `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:
 
@@ -212,6 +214,8 @@ If a required parent field is missing, CLI returns JSON error with exit code `2`
 
 - Use `survey.name` and `survey.recipient_type` (`title` is normalized to `name`).
 - `survey.recipient_type` must be `member`, `team`, or `org_wide`.
+- Survey results are written via `surveys.update` using nested `survey.survey_results_attributes`.
+- There is no standalone `createSurveyResult` / `updateSurveyResult` CLI command.
 - Valid `survey.name` values:
   - `employee_net_promoter_score`
   - `continuous_performance_review`
@@ -279,15 +283,16 @@ These wrap backend-owned markdown-tree primitives:
 - `tree` -> `markdownTreeSubtree`
 
 Discovery, ranking, canonical paths, and narrowing are backend-owned.
+An empty `find` result (`candidates: []`) means no evidence for that exact query/scope, not confirmed global absence.
 
 Ambiguity contract:
 
 - no silent bad guesses
 - returns `error.code = "ambiguous_match"` with ranked candidates in `error.details.candidates`
 
-## Notes Contract
+## Content Command Contract
 
-The `notes` command uses exact GraphQL operation names:
+The `content` command uses exact GraphQL operation names:
 
 - `CreateContent`
 - `UpdateContent`
@@ -297,31 +302,31 @@ The `notes` command uses exact GraphQL operation names:
 
 Placement rules enforced by command shape:
 
-- `notes create-member`
+- `content create-member`
   - `contentable_type: "Member"`
   - `contentable_id: TARGET_MEMBER_ID`
   - `member_id: TARGET_MEMBER_ID`
   - `focus_member_id: null`
   - `focus_team_id: null`
-- `notes create-manager`
+- `content create-manager`
   - `contentable_type: "Member"`
   - `contentable_id: ACTOR_MEMBER_ID`
   - `member_id: ACTOR_MEMBER_ID`
   - `focus_member_id: TARGET_MEMBER_ID`
-- `notes create-team`
+- `content create-team`
   - `contentable_type: "Team"`
   - `contentable_id: TEAM_ID`
   - `member_id: ACTOR_MEMBER_ID`
   - `focus_team_id: TEAM_ID`
-- `notes create-project`
+- `content create-project`
   - `contentable_type: "Project"`
   - `contentable_id: PROJECT_ID`
   - `member_id: ACTOR_MEMBER_ID`
-- `notes create-customer`
+- `content create-customer`
   - `contentable_type: "Customer"`
   - `contentable_id: CUSTOMER_ID`
   - `member_id: ACTOR_MEMBER_ID`
-- `notes create-contact`
+- `content create-contact`
   - `contentable_type: "Contact"`
   - `contentable_id: CONTACT_ID`
   - `member_id: ACTOR_MEMBER_ID`