@odla-ai/cli 0.48.4 → 0.49.0

package/dist/index.js

@@ -56,7 +56,7 @@ import {
   startHostedSecurityJob,
   surfacePaths,
   validateInvocation
-} from "./chunk-BD5KIG63.js";
+} from "./chunk-7627AY5G.js";
 import {
   exitCodeFor,
   redactSecrets

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@odla-ai/cli",
-  "version": "0.48.4",
+  "version": "0.49.0",
   "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",
@@ -58,7 +58,7 @@
     "prepublishOnly": "npm run build"
   },
   "dependencies": {
-    "@odla-ai/ai": "0.17.1",
+    "@odla-ai/ai": "0.17.2",
     "@odla-ai/apps": "0.15.1",
     "@odla-ai/brand": "0.8.1",
     "@odla-ai/db": "0.13.0",

package/skills/odla/SKILL.md

@@ -214,11 +214,15 @@ on the app. It is platform-side: there is nothing PM-specific to install or
 provision. Start a session by reading it, and keep it current while you build:
 
 ```cmd
-npx --yes @odla-ai/cli@latest pm next --app <appId>    # open goals, Ready, Doing
+npx --yes @odla-ai/cli@latest pm brief --app <appId>   # bounded counts + actionable windows
 npx --yes @odla-ai/cli@latest pm start --app <appId>   # claim the top Ready task
 ```
 
-`pm next` ends by naming the command to run next, and `pm start` claims Ready
+`pm brief` returns exact open-goal, Ready, Doing, current-principal, and bug
+counts with only the top actionable rows. Every omitted window names its full,
+scoped expansion command. `pm next --brief` and `pm handoff --brief` return the
+same projection; their defaults remain the existing full intake contracts.
+The briefing ends by naming the command to run next, and `pm start` claims Ready
 work in one call — it reads the current revision and compare-and-swaps against
 it server-side, so you never carry a revision between commands. It cannot mark
 work Ready: that contract is reviewed separately.
@@ -229,7 +233,7 @@ For a durable supervisor loop, establish and persist an exact-project PM cursor:
 npx --yes @odla-ai/cli@latest pm watch --app <appId> --entity task --jsonl
 ```
 
-A Ready event is a wake-up signal, not permission: re-read `pm next` and win the
+A Ready event is a wake-up signal, not permission: re-read `pm brief` and win the
 atomic claim before starting — `pm start` does both, against the revision that
 is current when it runs rather than the one the event carried. PM-attached
 comments use the same cursor (`--action comment.created`); general Discussion