@koda-sl/baker-cli 0.92.1 → 0.94.0

package/README.md

@@ -882,9 +882,13 @@ baker ads linkedin analytics
 baker ads linkedin analytics --level campaign --campaign-id 1234 \
   --pivot job-title --intent baseline --last-days 30
 
-# "Top companies seeing this campaign" (ABM feedback loop)
+# "Top companies seeing this campaign" (ABM feedback loop) — org names auto-resolved
 baker ads linkedin top-companies --campaign-id 1234 --last-days 30
 
+# "Who are these org URNs?" — resolve org URNs to company names (probe leakage)
+baker ads linkedin resolve --urns urn:li:organization:17719,urn:li:organization:19022
+baker ads linkedin resolve --ids 17719,19022 --output csv
+
 # "Who is in our audience by industry/seniority/function/title — all at once?"
 baker ads linkedin demographics --campaign-id 1234 --last-days 30
 
@@ -2311,8 +2315,11 @@ Manage action items for the current chat. Most write operations stage on the cha
 `BAKER_CHAT_ID` must be set for any command that stages or claims against a chat.
 
 ```bash
-baker actions list                         # default: bucketed (claimable, myClaims, blocked, claimedByOthers, completed, discarded)
+baker actions list                         # default: bucketed (claimable, myClaims, blocked, claimedByOthers, completed, discarded, draftCreates)
 baker actions list --bucketed=false --status pending
+# With BAKER_CHAT_ID, the bucketed list folds in THIS chat's draft: staged creates appear in
+# `draftCreates`; published actions being completed/discarded/updated carry a `draftStatus` marker.
+# Only the caller's own chat draft is reflected — never another chat's staged work.
 
 baker actions get <action-id>
 baker actions status temp_hero jx123       # batch resolve real IDs and temp_* refs
@@ -2322,15 +2329,25 @@ baker actions release <action-id>
 
 baker actions create --name "Build hero" --description "..."
 # → returns { ok, data: { tempId }, hints: [...] } — check hints for dependencies/description reminders
+# If the name/description reads as recurring or future-dated (e.g. "weekly", "every Monday", "schedule"),
+# create emits a hint to use `baker scheduled-actions create` instead of a Work Action.
 baker actions update <action-id> --name "Better name"
 baker actions complete <action-id-or-tempId> --note "What was done"  # stages — applies on chat publish
 baker actions discard <action-id> --reason "obsolete"
 
 baker actions link --blocker <id-or-tempId> --blocked <id-or-tempId>
 baker actions unlink --blocker <id> --blocked <id>
+
+# Review and edit the ops staged in THIS chat before publish
+baker actions draft                        # show every staged op + footgun warnings
+baker actions draft remove temp_hero        # drop a staged create (cascades its complete/link ops)
+baker actions draft remove <id> --op complete   # drop a staged op on a real action (--op update|complete|discard|tagAdd|tagRemove)
+baker actions draft clear                   # drop everything staged in this chat
 ```
 
-`baker actions status <ref...>` reads live Work Action status without requiring `BAKER_CHAT_ID`. It sends all refs in one request to `/api/actions/status` and preserves the backend JSON envelope:
+`baker actions draft` is the detailed, op-by-op view of staged (pre-publish) ops plus footgun `warnings`, and the place to edit the draft (`draft remove`/`clear`). The bucketed `list` and a chat-scoped `status` also surface this chat's draft (staged creates, `draftStatus` markers, `draft` ref status), so `draft` is mainly for the full changelog and edits. Do not stage `complete` to cancel an unwanted action — that publishes it as an already-completed item; remove the staged create (or `discard` a published action) instead.
+
+`baker actions status <ref...>` resolves refs in one request to `/api/actions/status`. It works without `BAKER_CHAT_ID`, but when the CLI has a chat id it includes it so a temp still staged in **that** chat resolves to `status: "draft"` instead of `not_found` (only the caller's own chat draft is consulted). It preserves the backend JSON envelope:
 
 ```json
 {
@@ -2342,10 +2359,16 @@ baker actions unlink --blocker <id> --blocked <id>
       "status": "completed",
       "name": "Build hero section"
     },
+    {
+      "ref": "temp_staged",
+      "status": "draft",
+      "name": "Brand new task",
+      "hint": "Created in this chat's draft, not yet published. It applies when this chat publishes."
+    },
     {
       "ref": "temp_old",
       "status": "not_found",
-      "hint": "Temp ref was not published, was discarded before publish, or belongs to another company."
+      "hint": "Temp ref was not published, was discarded before publish, does not exist, or belongs to another company."
     }
   ]
 }