@koda-sl/baker-cli 0.154.0 → 0.155.0

package/README.md

@@ -2495,9 +2495,16 @@ baker actions claim <action-id>            # live — returns action details + r
 baker actions release <action-id>
 
 baker actions create --name "Build hero" --priority high --tags landing,creative --description "..."
-# → returns { ok, data: { tempId }, hints: [...] } — check hints for tags/priority/dependencies/description reminders
+# → returns { ok, data: { tempId, draftCreateCount }, hints: [...] } — check hints for tags/priority/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.
+# If it instead names work a surface executes in-chat (a GTM container change, a site tag, an ad-platform
+# write, a page or form edit, or a value only the user has), create emits a do-it-now hint naming that
+# surface — doing the work is the default, an action is the exception. One advisory hint per call: the
+# scheduled redirect wins when both match.
+# `draftCreateCount` is how many creates this chat has staged (counted after this op, so it drops again
+# after `draft remove`). At 3 or more, create emits a fan-out hint: re-read the draft and merge actions
+# that touch the same system into one.
 # If no --tags are passed, create emits a MISSING --tags hint — the action is invisible to the backlog's tag filter.
 # If no --priority is passed, create emits a MISSING --priority hint — the action ranks as normal/medium in the do-first order.
 baker actions update <action-id> --name "Better name" --tags google-ads,strategy  # --tags REPLACES the set; '' clears