@odla-ai/cli 0.27.5 → 0.27.6

package/README.md

@@ -589,7 +589,7 @@ For parity with a static Google Appointment Schedule embed/link, set the public
 `bookingPageUrl` per environment. Provision applies it through the owner-only
 calendar settings route; it is public configuration, not a credential.
 
-`calendar status` returns the safe connection/sync projection; add `--json` for
+`calendar status` returns the safe connection/bookability projection; add `--json` for
 agent automation. Once connected, `calendar calendars` lists ids visible to the
 Google identity so the checked-in selection can be refined. `calendar connect`
 applies the checked-in booking-page setting and starts consent when the
@@ -609,14 +609,15 @@ authorization code, client secret, access token, or refresh token.
 
 The SDK uses the existing server-side db values (`ODLA_ENDPOINT`,
 `ODLA_TENANT`, `ODLA_API_KEY`), so calendar adds no Worker secret. Never expose
-`ODLA_API_KEY` to a browser. Trusted Worker code can initialize
-`@odla-ai/calendar`; browser code reads `$bookings` through `@odla-ai/db/client`
-under explicit rules or imports pure helpers from `@odla-ai/calendar/client`.
-
-These commands operate the current read/embed reconciliation slice. The CLI has
-no native slot-picker or create/reschedule/cancel command, and exposes no
-rolling-window/age-out, quota-backoff, retention/purge, or provider-derived
-mutation-id control. Public health remains aggregate rather than per calendar.
+`ODLA_API_KEY` to a browser. Trusted Worker code initializes
+`@odla-ai/calendar` for live FreeBusy/upcoming reads and idempotent
+create/reschedule/cancel operations; browser code imports only pure helpers and
+public configuration from `@odla-ai/calendar/client`.
+
+These CLI commands manage the provider connection and its non-secret calendar
+selection. They intentionally do not create or mutate events: application
+backends do that through `@odla-ai/calendar`. Google is the source of truth and
+odla stores no event or attendee mirror.
 
 The bundled build/migration skills add a passive pre-ship gate with
 `@odla-ai/security`: install it with a normal development range, commit the

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@odla-ai/cli",
-  "version": "0.27.5",
-  "description": "Agent-operable CLI for odla provisioning, calendar consent and sync lifecycle, System AI administration, Worker secrets, security jobs, and smoke checks.",
+  "version": "0.27.6",
+  "description": "Agent-operable CLI for odla provisioning, calendar consent and connection lifecycle, System AI administration, Worker secrets, security jobs, and smoke checks.",
   "license": "MIT",
   "homepage": "https://odla.ai/docs/packages/cli",
   "repository": {