@odla-ai/cli 0.27.6 → 0.27.8

package/dist/index.js

@@ -57,7 +57,7 @@ import {
   startHostedSecurityJob,
   surfacePaths,
   validateInvocation
-} from "./chunk-DQOJ4S6H.js";
+} from "./chunk-MZSU4YQL.js";
 export {
   AGENT_HARNESSES,
   CAPABILITIES,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@odla-ai/cli",
-  "version": "0.27.6",
+  "version": "0.27.8",
   "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",

package/skills/odla/SKILL.md

@@ -115,6 +115,7 @@ guessing which platform/credential steps need manual work. Then:
    `--wait <seconds>`); exit code 75 means still pending: the handshake is
    persisted, so once the human approves, re-run the same command and it
    resumes the same code and collects the token. It creates the app,
+   consuming a one-time exact-id reservation when the approved app is new,
    enables services, issues or reuses configured credentials (db key + o11y
    ingest token when enabled), composes declared integration schema/rules and
    guarded seeds, writes `.dev.vars`, and

package/skills/odla/references/agent-identity.md

@@ -112,8 +112,14 @@ permanent authority.
 - Wrong handle requested: decline it and correct the project/SDK request before
   starting a fresh handshake. If already approved, revoke the new credential in
   Studio; do not rename or merge principals by editing local metadata.
-- Missing project after reconnect: start a new reviewed handshake and select the
-  exact project; never widen to all projects.
+- Missing project on first provision: approve the exact id. Collection records
+  a one-time reservation; the credential creates only that app and Registry
+  binds the grant to its new incarnation. Never pre-create a substitute or
+  widen to all projects. The reservation does not bypass later service,
+  configuration, or administrative capability checks.
+- Approval returns 404: treat it as a Registry routing regression, not a missing
+  project outcome. Preserve the code and pending state, report the incident,
+  and retry the same request after Registry is healthy.
 - Project ownership/lifecycle changed after approval: collection expires the
   unusable replacement while preserving the current credential and grant set.
   Restore the intended project state, then start and review a fresh handshake.

package/skills/odla/references/build.md

@@ -55,7 +55,8 @@ The email is an account identifier, never a password or session credential.
 Prints a short device code and a link. ⏸ That same account opens the link, signs
 in, explicitly reviews the exact code, and approves it — loading the URL alone
 does not claim access, and no secret passes through the chat. Provision then:
-creates the app, enables its services, issues or reuses the db key (and the
+creates the app (consuming the approved one-time exact-id reservation when it
+is new), enables its services, issues or reuses the db key (and the
 o11y ingest token when o11y is enabled), pushes the composed app + integration
 schema/rules, creates missing guarded seeds, writes
 `.dev.vars`, and transfers configured Worker secrets through Wrangler stdin.
@@ -64,6 +65,14 @@ Local credential files are `0600` and gitignored. Verify with
 anything unset. `--push-secrets` preflights the Wrangler config and login before
 issuing or rotating a shown-once credential.
 
+If Studio shows an unknown exact app id, that is a valid first provision: the
+human approves the id, the collected credential creates only that app, and the
+grant becomes bound to its new incarnation. Do not pre-create a substitute app
+or broaden the request. A 404 from **Approve** is a platform regression; capture
+the code and retry only after Registry is healthy. This reservation covers only
+the exact app creation; service, configuration, and administrative mutations
+retain their ordinary capability and human-checkpoint requirements.
+
 Calendar adds a second ⏸ checkpoint after the odla device approval: provision
 prints/opens a state-bound Google URL issued by the platform and waits while
 the human grants the booking scopes in a browser. The CLI never receives the