@odla-ai/cli 0.25.23 → 0.26.1

package/README.md

@@ -156,6 +156,25 @@ therefore compares that verified expectation with the Worker answering now and
 reports `matched`, `drifted`, or `unknown`; an empty or unavailable receipt
 ledger degrades instead of silently treating observed health as intended state.
 
+Platform maintainers can rotate the built-in Discussion responder without
+minting an unrestricted app key or exposing the replacement in argv/output:
+
+```bash
+npx @odla-ai/cli platform chat-credentials rotate \
+  --wrangler-config packages/chat-agent/wrangler.jsonc \
+  --expected-version <deployed-chat-version-id> \
+  --email <odla-admin-account> \
+  --yes --json
+```
+
+The command requests only `platform:chat:credential:write`, mints an
+`agent_odla` key restricted to the Discussion namespaces and write envelope,
+pipes the nested `ODLA_BOT_TOKENS` map to Wrangler over stdin, and succeeds only
+after the service-binding health bridge advances from the pre-rotation Worker
+version to a healthy secret-change deployment. `--expected-version` fences the
+pre-rotation version before any credential is minted. Superseded keys are
+revoked separately after that health proof.
+
 For repository-managed settings, compare checked-in intent with the live
 owner-visible Registry projection before provisioning:
 
@@ -192,7 +211,11 @@ 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;
+canonical environment-settings recovery URL. Studio preserves the exact
+operation id in that URL and renders the matching
+`operations get <id> --json` recovery command. Plans that require Studio now
+link to the explicit app/environment settings scope instead of an ambiguous
+app-level Settings page. `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
@@ -227,7 +250,10 @@ npx @odla-ai/cli runbook edit db --note "retract replaced the null write"
 
 Platform runbook edits need admin or the `platform:runbook:write` capability,
 which the CLI requests for you; a plain handshake token is never admin by
-design, and `odla-ai whoami` reports what this terminal actually holds.
+design. `odla-ai whoami` reports the actual credential-bound principal by
+friendly name, handle, and kind; an agent's manager; the credential kind; and
+the accountable human owner separately. Manager metadata explains organization
+but never grants authority.
 
 **Is the corpus itself still true?**
 
@@ -503,6 +529,10 @@ claimable Studio request, and the public start/poll shape intentionally does not
 reveal whether an account exists. The signed-in matching user must explicitly
 review the exact code before it becomes pending, and only one claimed pending
 or approved-but-uncollected request can be active for that user.
+For an ordinary request, Studio also requires at least one exact project
+selection. The credential receives project metadata, PM, discussion, and
+brand-candidate editing grants only for those projects, never ambient owner
+access, app administration, or brand approval.
 
 Developer grants are tracked by id, owner, label, scopes, creation/expiry,
 last use, and revocation state. The plaintext token is delivered once to the