@koda-sl/baker-cli 0.98.1 → 0.99.0

package/README.md

@@ -2341,6 +2341,14 @@ baker actions list --bucketed=false --sort priority   # flat list, do-first orde
 # `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 log                          # actions COMPLETED today, newest first, each with its completion note
+baker actions log --since 7d               # completed in the last 7 days (today | yesterday | <N>d; default today)
+baker actions log --from 2026-06-01 --to 2026-06-15   # explicit ISO window (overrides --since; --to defaults to now)
+# Use this to report to the client what was done. `data` is an array of { action, assignee } —
+# the note and metadata live on `action` (e.g. data[].action.completedNote — the mandatory
+# description from `complete` — plus action.completedAt, action.tags, action.priority). Windows are local time.
+# Only PUBLISHED completions appear — ops staged in an unpublished chat are not included.
+
 baker actions get <action-id>
 baker actions status temp_hero jx123       # batch resolve real IDs and temp_* refs
 
@@ -2356,6 +2364,8 @@ baker actions create --name "Build hero" --priority high --tags landing,creative
 baker actions update <action-id> --name "Better name" --tags google-ads,strategy  # --tags REPLACES the set; '' clears
 baker actions update <action-id> --priority urgent                              # urgent|high|medium|low; 'none' clears
 baker actions complete <action-id-or-tempId> --note "What was done"  # stages — applies on chat publish
+# --note is REQUIRED (≥20 chars): what changed, where, and the outcome. It is the durable, client-facing
+# record surfaced by `baker actions log`. A missing/too-short note is rejected with a VALIDATION_ERROR.
 baker actions discard <action-id> --reason "obsolete"
 
 # Tags — taxonomy is built-in defaults + company custom tags; --tags is STRICT (unknown slugs are rejected)