@greatwait/cli 0.1.0-alpha.8 → 0.2.0

package/README.md

@@ -6,7 +6,6 @@ against a receiver you control.
 ```sh
 npm install --global @greatwait/cli
 greatwait login --api-url https://api.greatwait.dev
-greatwait journey
 ```
 
 ## What it is
@@ -44,18 +43,59 @@ directory, readable by you and nobody else. A staging credential is never
 presented to production, because the two are separate entries rather than one
 current context.
 
-## First value
+## First callback
 
-`greatwait journey` prints the published first-value sequence — the same nine
-steps the website and the quickstarts walk — with the command for each one.
+Use a public HTTPS receiver you control. Once signed in, schedule directly to
+its URL and wait for the first delivery:
 
 ```sh
-greatwait destinations create --url https://your-receiver.example.com/greatwait
-greatwait schedules create --endpoint ep_… --in 30s --data '{"greeting":"first value"}'
-greatwait occurrences wait sch_… occ_…
-greatwait attempts list sch_… occ_…
+greatwait schedules create --url https://your-receiver.example.com/greatwait --in 30s --data '{"hello":"world"}' --wait
 ```
 
+GreatWait uses your project's destination at that URL or creates one. The
+answer includes the schedule and occurrence ids; copy them into the read:
+
+```sh
+greatwait attempts list <schedule> <occurrence>
+```
+
+Look for `state: succeeded` and the status your receiver returned. `--wait`
+stops after three minutes by default; a settled failure is also an outcome,
+so inspect the attempt. If it times out, use
+`greatwait occurrences wait <schedule> <occurrence>` and read the attempts
+again. The timeout does not cancel the scheduled call.
+
+For a signed receiver, first add your URL in
+[Settings → Endpoints](https://app.greatwait.dev/settings/endpoints), reveal its
+signing secret, and configure the receiver. The direct-URL schedule reuses that
+destination. If the schedule already created it, reveal the secret and configure
+the receiver before its due time; use a longer `--in` if needed. Direct-URL
+scheduling never prints the signing secret. Verify the signature over the exact request bytes
+before parsing, as described in the
+[CLI quickstart](https://docs.greatwait.dev/guides/cli).
+
+## Clean up
+
+Archive the finished schedule. Read it to find its destination id:
+
+```sh
+greatwait schedules read <schedule>
+greatwait schedules archive <schedule>
+```
+
+If this walkthrough created the destination and no other schedule uses it,
+disable it:
+
+```sh
+greatwait destinations disable <destination> --yes
+```
+
+If you stop before delivery, cancel the schedule with
+`greatwait schedules cancel <schedule> --yes` first. Revoke a walkthrough API
+key in the dashboard, or use `greatwait credentials revoke <credential> --yes`
+while signed in through OAuth. Finish with `greatwait logout` to revoke the CLI
+grant and remove local credentials.
+
 ## Output and exit codes
 
 `--json` is a versioned machine shape, not a serialization of the human text.

package/package.json

@@ -7,10 +7,10 @@
     "url": "https://github.com/flowxo/greatwait/issues"
   },
   "dependencies": {
-    "@greatwait/api-client": "0.1.0-alpha.8",
-    "@greatwait/contracts": "0.1.0-alpha.8"
+    "@greatwait/api-client": "0.2.0",
+    "@greatwait/contracts": "0.2.0"
   },
-  "description": "The GreatWait command line: sign in, create a destination and a one-shot schedule, and wait for the callback, over the public API.",
+  "description": "The GreatWait command line: sign in, schedule a call to a URL, and read its delivery outcome over the public API.",
   "engines": {
     "node": ">=22.13.0"
   },
@@ -48,5 +48,5 @@
   },
   "sideEffects": false,
   "type": "module",
-  "version": "0.1.0-alpha.8"
+  "version": "0.2.0"
 }