@odla-ai/cli 0.25.19 → 0.25.21

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.
package/README.md CHANGED
@@ -79,6 +79,7 @@ ODLA_DEV_TOKEN=... npx @odla-ai/cli pm handoff --app <appId>
79
79
  ODLA_DEV_TOKEN=... npx @odla-ai/cli discuss list --app <appId> --json
80
80
  ODLA_DEV_TOKEN=... npx @odla-ai/cli o11y status --app <appId> --env prod --json
81
81
  ODLA_DEV_TOKEN=... npx @odla-ai/cli whoami --json
82
+ npx @odla-ai/cli platform status --context production --json
82
83
  npx @odla-ai/cli pm handoff --context production --json
83
84
  npx @odla-ai/cli runbook new deploy --context production --title Deploy --file deploy.md
84
85
  ```
@@ -141,6 +142,17 @@ jobs, missing canary configuration, stale probes, and partial
141
142
  socket-reconciliation coverage remain explicit fields. Authentication progress
142
143
  is stderr-only, so stdout is a single JSON document.
143
144
 
145
+ For platform-wide operations, `platform status --json` requests only the
146
+ short-lived, admin-approved `platform:status:read` capability and reads the
147
+ same `odla.platform-status/v1` snapshot as Studio. It works outside a project
148
+ checkout, derives its complete six-Worker inventory from the deployment
149
+ catalog, probes private services over bindings, and joins observed release
150
+ identity with retained Cloudflare request/error/CPU/wall-time/memory evidence.
151
+ Unavailable health, credentials, versions, or provider snapshots remain
152
+ explicit rather than becoming zero; the document includes stable reason codes
153
+ and exact next actions. Expected release and drift stay `unknown` until durable
154
+ deployment receipt reads are added.
155
+
144
156
  **Runbooks are procedure; JSDoc is API.** What a function takes, returns, and
145
157
  guarantees is documented on the export itself, ships in the installed
146
158
  `.d.ts`, and renders per package at <https://odla.ai/docs>. A runbook will tell
@@ -746,6 +758,12 @@ export default {
746
758
  `db.schema` and `db.rules` may be inline objects, JSON files, or JS modules
747
759
  exporting `default`, `schema` / `SCHEMA`, or `rules` / `RULES`.
748
760
 
761
+ `services` accepts only ids from `@odla-ai/apps`'
762
+ `APP_SERVICE_CATALOG`. The CLI validates the same-environment dependencies
763
+ from that catalog before authentication or mutation; currently `calendar`,
764
+ `chat`, and `kg` require `db`. Application npm integrations remain under
765
+ `integrations`, not `services`.
766
+
749
767
  If schema is present and rules are omitted, `defaultRules: "deny"` generates
750
768
  deny-all rules for every schema entity. That is the safe default for Workers
751
769
  that mediate reads and writes with an app key.