@odla-ai/cli 0.25.18 → 0.25.20

package/README.md

@@ -266,13 +266,13 @@ npx odla-ai security sources --env dev
 npx odla-ai security run --source <source-id> --ref main --env dev --plan-digest <digest-from-security-plan> --ack-redacted-source
 npx odla-ai security status <job-id>
 npx odla-ai security report <job-id>
-npx odla-ai admin ai show --email owner@example.com
-npx odla-ai admin ai models
-npx odla-ai admin ai set security --discovery-provider anthropic --discovery-model claude-opus-4-8 --validation-provider openai --validation-model gpt-5.5 --enabled
-npx odla-ai admin ai credentials
-npx odla-ai admin ai credential set anthropic --from-env ANTHROPIC_API_KEY
-npx odla-ai admin ai usage --app-id my-app --env prod --limit 50
-npx odla-ai admin ai audit --limit 25
+npx odla-ai admin ai show --context production --email owner@example.com
+npx odla-ai admin ai models --context production
+npx odla-ai admin ai set security --context production --discovery-provider anthropic --discovery-model claude-opus-4-8 --validation-provider openai --validation-model gpt-5.5 --enabled
+npx odla-ai admin ai credentials --context production
+npx odla-ai admin ai credential set anthropic --context production --from-env ANTHROPIC_API_KEY
+npx odla-ai admin ai usage --context production --app-id my-app --env prod --limit 50
+npx odla-ai admin ai audit --context production --limit 25
 npx odla-ai skill install
 npx odla-ai version
 ```
@@ -598,7 +598,9 @@ truncated work stays visible.
 
 `admin ai show|models|set|credentials|credential set|usage|audit` manages platform-funded System
 AI (`o11y.triage`, `security.discovery`, `security.validation`). It uses a
-separate, mode-`0600` `.odla/admin-token.local.json` cache. Studio displays the
+separate, mode-`0600` scoped-grant cache: beneath the selected named context,
+the project root when a config is loaded, or the global operator directory
+otherwise. It never follows an arbitrary shell working directory. Studio displays the
 exact scope, only an admin can approve it, and it expires after ~15 minutes;
 policy, credential, and usage capabilities are separate and cannot act as the
 approver on ordinary app/db/o11y routes. `admin ai models` reads the server
@@ -744,6 +746,12 @@ export default {
 `db.schema` and `db.rules` may be inline objects, JSON files, or JS modules
 exporting `default`, `schema` / `SCHEMA`, or `rules` / `RULES`.
 
+`services` accepts only ids from `@odla-ai/apps`'
+`APP_SERVICE_CATALOG`. The CLI validates the same-environment dependencies
+from that catalog before authentication or mutation; currently `calendar`,
+`chat`, and `kg` require `db`. Application npm integrations remain under
+`integrations`, not `services`.
+
 If schema is present and rules are omitted, `defaultRules: "deny"` generates
 deny-all rules for every schema entity. That is the safe default for Workers
 that mediate reads and writes with an app key.