@wave-ai-os/wave-cli 0.1.67 → 0.1.70

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -14,7 +14,7 @@ See also:
14
14
  - Help output is human-readable and exits `0`; it does not emit a JSON error envelope.
15
15
  - `--readable` enables human formatting where a command supports it; `--json` forces the stable machine envelope where both flags are present.
16
16
  - No prompts, colors, or implicit interactive UX in this phase.
17
- - JWT forwarding is centralized.
17
+ - Token handling is centralized and credentials are never printed in envelopes.
18
18
 
19
19
  ## Install
20
20
 
@@ -167,6 +167,33 @@ Namespace taxonomy:
167
167
 
168
168
  `wave doctor` is read-only. It checks auth token resolution, organization ID resolution, base URL resolution, GraphQL reachability, API JSON response health, optional OpenAPI contract configuration, and CLI runtime integrity.
169
169
 
170
+ ### Fixed machine protocol
171
+
172
+ Remote adapters can discover the complete supported surface through `wave api ls --json`.
173
+ Its `data.operations` array is generated from the registered Commander action tree and
174
+ includes every invocable command, JSON input/output schemas, examples, explicit
175
+ classification, approval requirement, machine capabilities, CLI version, and a
176
+ registry digest. `data.commands` is a compatibility projection derived from that same
177
+ manifest.
178
+
179
+ The only machine invocation shape is:
180
+
181
+ ```bash
182
+ printf '%s' '{"id":"123"}' | wave --machine execute \
183
+ --operation projects.show \
184
+ --phase validate \
185
+ --input-json -
186
+ ```
187
+
188
+ `validate` checks and normalizes JSON input without accessing a Wave record.
189
+ `preview` is available only for writes and returns the exact command plus validated
190
+ input. `execute` accepts no raw shell command or user-supplied CLI flags. Read and
191
+ write execution requires a trusted, OAuth-bound machine-auth envelope; writes also
192
+ require a server-managed approval bound to the operation, normalized-input digest,
193
+ CLI version, registry digest, organization, and actor. Machine mode clears ambient
194
+ Wave configuration and local credential storage before dispatch, so it cannot inherit
195
+ a developer's local session.
196
+
170
197
  ## Commands
171
198
 
172
199
  Examples: