@odla-ai/cli 0.25.22 → 0.25.23

package/README.md

@@ -161,10 +161,12 @@ owner-visible Registry projection before provisioning:
 
 ```bash
 npx odla-ai config diff --json
-npx odla-ai config plan --json
+npx odla-ai config plan --json > .odla/config-plan.json
+npx odla-ai config apply --plan .odla/config-plan.json --json
+npx odla-ai operations wait <operation-id> --json
 ```
 
-Both commands are read-only and request only a short-lived,
+`diff` and `plan` are read-only and request only a short-lived,
 owner-approvable `app:config:read` capability. It opens only exact-id
 `GET /registry/apps/<appId>` reads for apps the approver owns; app listing,
 writes, PM, Discussions, directory access, data-plane delegation, and every
@@ -174,14 +176,29 @@ status, field provenance, and a bounded coverage declaration. Runtime auth or
 links omitted from project config stay visible as `unmanaged` rather than
 being silently overwritten.
 
-`plan` freezes those revisions plus ordered actions into a stable plan digest.
+`plan` v2 freezes those content revisions, the monotonic Registry
+`registry:<number>` revision, and ordered actions into a stable digest.
 Enable/configure actions are dependency-first; proposed disablements are
-dependent-first, high-risk, approval-required, and Studio-only. Conditional,
-resumable `config apply` is intentionally not exposed yet. The plan names the
-existing provision, rename, and Studio steps that can be reviewed separately,
-and explicitly excludes schema, rules, integration seeds, credentials, vault
-or Worker secrets, OAuth connection state, and opaque controller-assigned
-service fields rather than claiming whole-system convergence.
+dependent-first, high-risk, approval-required, and Studio-only.
+
+`config apply` accepts only that saved JSON plan. Before requesting authority it
+recomputes the digest, verifies the selected app/platform, confirms checked-in
+intent has not changed, and rejects every production, destructive,
+approval-marked, high-risk, Studio, auth, creation, or disable action. The
+short-lived `app:config:write` grant reaches only this app's operation
+reserve/resume/read routes; it cannot enumerate apps or call direct mutation
+routes. A deterministic default idempotency key makes retrying the same plan
+resume the same durable journal entry, while the Registry CAS revision rejects
+stale state.
+
+Apply prints the operation receipt, including ordered step attempts and its
+Studio recovery URL. `operations get` reads one exact id without replaying it;
+`operations wait` polls that id for 60 seconds by default (`--timeout` and
+`--interval` are explicit seconds). A still-running bounded wait exits 75 after
+printing its last receipt. Every terminal receipt is independently
+digest-verified by the CLI before success. Schema, rules, integration seeds,
+credentials, vault or Worker secrets, OAuth connection state, and opaque
+controller-assigned service fields remain outside this boundary.
 
 **Runbooks are procedure; JSDoc is API.** What a function takes, returns, and
 guarantees is documented on the export itself, ships in the installed
@@ -284,7 +301,10 @@ npx odla-ai setup
 npx odla-ai init --app-id my-app --name "My App"
 npx odla-ai doctor
 npx odla-ai config diff --json
-npx odla-ai config plan --json
+npx odla-ai config plan --json > .odla/config-plan.json
+npx odla-ai config apply --plan .odla/config-plan.json --json
+npx odla-ai operations get <operation-id> --json
+npx odla-ai operations wait <operation-id> --timeout 60 --json
 npx odla-ai calendar status --env dev
 npx odla-ai calendar calendars --env dev
 npx odla-ai calendar connect --env dev