@koda-sl/baker-cli 0.134.1 → 0.135.1-dev.46c403ad4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -2507,7 +2507,8 @@ Permissions enforced server-side:
2507
2507
 
2508
2508
  - Only `claim`/`release` mutate live state.
2509
2509
  - `claim` returns action details (`id`, `name`, `description`) plus `recommendedSkills` — a fast model reads the action's name/description/tags against the local `.claude/skills/` catalog and returns the skills (`{ name, reason }`) most worth loading for the work, echoed as `/skill — reason` lines in `hints`. It is best-effort: if the catalog is absent or the model call fails, the claim still succeeds and falls back to the generic "review and load relevant skills" hint.
2510
- - `update`, `complete`, `discard`, `unlink` require the action to be claimed by the current chat — otherwise the API returns `FORBIDDEN` with a hint to claim first.
2510
+ - `complete` and `unlink` require the action to be claimed by the current chat — otherwise the API returns `FORBIDDEN` with a hint to claim first. Completing is the record that the work is done, so it stays claim-gated.
2511
+ - `update` and `discard` do NOT require a claim — a chat may edit or retire an action it never claimed. They are blocked only when another chat currently holds the claim (`CONFLICT` with that chat's title).
2511
2512
  - Claiming an action already claimed by another chat returns `CONFLICT` with the other chat's title — pick a different action.
2512
2513
  - All staged ops are reverted automatically when the chat is discarded.
2513
2514
 
@@ -2535,6 +2536,64 @@ baker mcp remove --name weather
2535
2536
 
2536
2537
  ---
2537
2538
 
2539
+ ### `baker history list`
2540
+
2541
+ Unified account history (audit log) — everything that changed on the account, newest first: publishes, chat lifecycle, backlog actions, team changes, setup links, tag and schedule changes, executed ad-platform writes, followed advertisers, media (images, videos, testimonials), creative generations, reports, domains, integrations, and API keys. Read-only.
2542
+
2543
+ ```bash
2544
+ baker history list # last 30 changes, compact
2545
+ baker history list --limit 50 --days 7 # last week, up to 50 entries
2546
+ baker history list --category publish # only publishes
2547
+ baker history list --category ads --full # ad writes with raw metadata
2548
+ ```
2549
+
2550
+ **Flags:**
2551
+
2552
+ | Flag | Description |
2553
+ |--------------|----------------------------------------------------------------------|
2554
+ | `--limit` | Max entries, 1-200 (default 30) |
2555
+ | `--category` | one of: publish, chat, action, team, setup_link, company, tag, schedule, ads, advertiser, media, creative, report, domain, integration |
2556
+ | `--days` | Only entries from the last N days (1-365) |
2557
+ | `--full` | Include raw metadata per entry |
2558
+
2559
+ **Response:**
2560
+
2561
+ ```json
2562
+ {
2563
+ "ok": true,
2564
+ "data": {
2565
+ "entries": [
2566
+ { "id": "…", "at": 1750000000000, "category": "publish", "action": "publish.commit", "actorType": "user", "actor": "Jane Doe", "target": "Update hero copy" }
2567
+ ]
2568
+ },
2569
+ "meta": { "count": 1 }
2570
+ }
2571
+ ```
2572
+
2573
+ ---
2574
+
2575
+ ### `baker chats list | view | transcript | diff`
2576
+
2577
+ Read-only inspection of **other Sessions (chats) on the same account** — so an agent can reuse prior work ("like we did in that other chat, but for X"). Same-account only; never crosses a company boundary and has no write surface.
2578
+
2579
+ ```bash
2580
+ baker chats list # other Sessions, newest first (all statuses)
2581
+ baker chats list --status active # only running Sessions
2582
+ baker chats view <id> # kickoff, outputs (changes), threads, commits
2583
+ baker chats transcript <id> --full # read the conversation, verbatim
2584
+ baker chats diff <id> --surface landings # real file-level changes, landings only
2585
+ baker chats diff <id> --full # include the unified-diff patch text
2586
+ ```
2587
+
2588
+ **`list` flags:** `--status active|archived|all` (default `all`), `--limit` (1-100, default 20), `--full` (include each Session's full change list).
2589
+ **`view`:** returns the unified `effects` — git content (`content`, `creatives`) AND DB-only effects that never touch the repo (`actions`, `scheduledActions`, `tags`, `ads.{google,meta,linkedin}`), each resolved to real detail and flagged `staged` (in-progress draft) vs applied. Plus `kickoff`, `outputs` counts, `threads`, `commits`, `diffAvailable`.
2590
+ **`transcript` flags:** `--limit` (1-1000, default 100, most recent), `--full` (untruncated text). Returns `entries` (`role` + `text`) and `truncated`.
2591
+ **`diff` flags:** `--surface knowledge|company|brand|landings|flows|creatives`, `--full` (patch text per file). Returns `available`, `files` (`path`, `surface`, `status`, `additions`, `deletions`, `patch`).
2592
+
2593
+ A Session's effects live in two places: **git content** (files — landings, creatives, flows, brand, knowledge) and **DB-only effects** (Actions, Tags, ad-platform writes — never in the repo). `view` unifies BOTH. `diff` only covers the git content (the actual file patches) and only for a published Session; in-progress Sessions have no reachable file diff (`available: false`) — but `view` still shows their staged DB effects. Use `view` for the complete picture, `diff` to read the real file content.
2594
+
2595
+ ---
2596
+
2538
2597
  ### `baker schema [command]`
2539
2598
 
2540
2599
  Inspect command argument schemas for AI agent introspection.
@@ -7,9 +7,9 @@ import {
7
7
  __toESM
8
8
  } from "./chunk-RK67WL4O.js";
9
9
 
10
- // ../../node_modules/.pnpm/safe-stable-stringify@2.5.0/node_modules/safe-stable-stringify/index.js
10
+ // ../../.pnpm-store/v10/links/@/safe-stable-stringify/2.5.0/810146e81bae4e3a061fe487864f2fde80c4b03b886877dc0f1fffbc6480b67e/node_modules/safe-stable-stringify/index.js
11
11
  var require_safe_stable_stringify = __commonJS({
12
- "../../node_modules/.pnpm/safe-stable-stringify@2.5.0/node_modules/safe-stable-stringify/index.js"(exports, module) {
12
+ "../../.pnpm-store/v10/links/@/safe-stable-stringify/2.5.0/810146e81bae4e3a061fe487864f2fde80c4b03b886877dc0f1fffbc6480b67e/node_modules/safe-stable-stringify/index.js"(exports, module) {
13
13
  "use strict";
14
14
  var { hasOwnProperty } = Object.prototype;
15
15
  var stringify = configure2();
@@ -1034,7 +1034,7 @@ function resolveAdaptFormats(params) {
1034
1034
  return params.formats ?? [];
1035
1035
  }
1036
1036
 
1037
- // ../../node_modules/.pnpm/safe-stable-stringify@2.5.0/node_modules/safe-stable-stringify/esm/wrapper.js
1037
+ // ../../.pnpm-store/v10/links/@/safe-stable-stringify/2.5.0/810146e81bae4e3a061fe487864f2fde80c4b03b886877dc0f1fffbc6480b67e/node_modules/safe-stable-stringify/esm/wrapper.js
1038
1038
  var import__ = __toESM(require_safe_stable_stringify(), 1);
1039
1039
  var configure = import__.default.configure;
1040
1040
  var wrapper_default = import__.default;
@@ -7798,4 +7798,4 @@ export {
7798
7798
  defaultRegistry,
7799
7799
  createEngineFromEnv
7800
7800
  };
7801
- //# sourceMappingURL=chunk-CIF62V7L.js.map
7801
+ //# sourceMappingURL=chunk-GKL4CUCC.js.map