@odla-ai/cli 0.32.1 → 0.34.0

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.
@@ -283,6 +283,16 @@ it later.
283
283
  service credentials. After `provision --push-secrets`, use
284
284
  `npx @odla-ai/cli smoke --env dev --runtime`; it verifies the Worker and
285
285
  anonymous integration routes without retrieving its db/o11y secrets.
286
+ When `o11y.monitoring` is configured, apply its repository-owned Kitesurf or
287
+ existing-o11y performance indicators, cadence, SLOs, and email schedule with `monitor plan` followed by
288
+ `monitor apply` (`--yes` for prod). For unattended diagnosis, prefer
289
+ `monitor status --json`, `monitor incidents --runs --json`, and
290
+ `monitor report --period weekly --json`. Treat `bad` as application evidence;
291
+ `monitor_error` and `missed` mean the monitoring system is uncertain and must
292
+ not be reported as app downtime or success; this includes no request data and
293
+ stale canaries. The returned documents deliberately exclude page content. Use
294
+ `monitor run <probe-id> --json` for a bounded manual Kitesurf check;
295
+ manual outcomes never enter the scheduled SLO denominator.
286
296
  Use `calendar status --json` for safe connection state (`bookable`, booking
287
297
  and availability calendars) and `calendar calendars --json` to discover ids
288
298
  after consent; update checked-in config and re-provision. Disconnect always