@koda-sl/baker-cli 0.338.0 → 0.339.0

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
@@ -3651,7 +3651,7 @@ baker chats diff <id> --live # in-progress Session: read from its l
3651
3651
  ```
3652
3652
 
3653
3653
  **`list` flags:** `--status active|archived|all` (default `all`), `--limit` (1-100, default 20), `--full` (include each Session's full change list).
3654
- **`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`.
3654
+ **`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,x}`, `tagManager`, `ga4`, `funnel` (with the ways in it added or removed, `triggersAdded`/`triggersRemoved`), `conversions`, `conversionSends`, `eventSources`), plus `otherChanges` for every other change the Session made (A/B tests, recipes, library images), each resolved to real detail and flagged `staged` (in-progress draft) vs applied. Plus `kickoff`, `outputs` counts, `threads`, `commits`, `diffAvailable`.
3655
3655
  **`transcript` flags:** `--limit` (1-1000, default 100, most recent), `--full` (untruncated text). Returns `entries` (`role` + `text`) and `truncated`.
3656
3656
  **`diff` flags:** `--surface knowledge|company|brand|landings|flows|creatives`, `--full` (patch text per file), `--live` (read an in-progress Session's changes from its live workspace). Returns `available`, `source` (`published`|`live`), `files` (`path`, `surface`, `status`, `additions`, `deletions`, `patch`), and `truncated` when a large live diff was capped.
3657
3657
 
package/dist/cli.js CHANGED
@@ -5061,6 +5061,40 @@ var creativeEffectSchema = z13.object({
5061
5061
  title: z13.string().nullable(),
5062
5062
  status: z13.string().nullable()
5063
5063
  });
5064
+ var settingOutcomeSchema = z13.enum(["applied", "skipped", "refused"]).nullable();
5065
+ var funnelTriggerRefSchema = z13.object({ step: z13.string(), trigger: z13.string() });
5066
+ var funnelEffectSchema = z13.object({
5067
+ op: effectOpSchema,
5068
+ staged: z13.boolean(),
5069
+ summary: z13.string(),
5070
+ added: z13.array(z13.string()),
5071
+ changed: z13.array(z13.string()),
5072
+ removed: z13.array(z13.string()),
5073
+ /** Each way in the proposal adds, named by step and event key. */
5074
+ triggersAdded: z13.array(funnelTriggerRefSchema),
5075
+ /** Each way in the proposal takes away, named by step and event key. */
5076
+ triggersRemoved: z13.array(funnelTriggerRefSchema),
5077
+ outcome: settingOutcomeSchema,
5078
+ /** Why it was refused or skipped. Null when it applied or is still staged. */
5079
+ reason: z13.string().nullable()
5080
+ });
5081
+ var settingEffectSchema = z13.object({
5082
+ op: effectOpSchema,
5083
+ staged: z13.boolean(),
5084
+ subject: z13.string(),
5085
+ summary: z13.string(),
5086
+ outcome: settingOutcomeSchema,
5087
+ reason: z13.string().nullable()
5088
+ });
5089
+ var listedChangeEffectSchema = z13.object({
5090
+ surface: chatChangeTypeSchema,
5091
+ slug: z13.string(),
5092
+ op: effectOpSchema,
5093
+ staged: z13.boolean(),
5094
+ title: z13.string().nullable(),
5095
+ /** Why Publish could not apply it, when the row records that. */
5096
+ reason: z13.string().nullable()
5097
+ });
5064
5098
  var chatEffectsSchema = z13.object({
5065
5099
  content: z13.array(contentEffectSchema),
5066
5100
  actions: z13.array(actionEffectSchema),
@@ -5074,7 +5108,12 @@ var chatEffectsSchema = z13.object({
5074
5108
  }),
5075
5109
  creatives: z13.array(creativeEffectSchema),
5076
5110
  tagManager: z13.array(configEffectSchema),
5077
- ga4: z13.array(configEffectSchema)
5111
+ ga4: z13.array(configEffectSchema),
5112
+ funnel: z13.array(funnelEffectSchema),
5113
+ conversions: z13.array(settingEffectSchema),
5114
+ conversionSends: z13.array(settingEffectSchema),
5115
+ eventSources: z13.array(settingEffectSchema),
5116
+ otherChanges: z13.array(listedChangeEffectSchema)
5078
5117
  });
5079
5118
  var publishSurfaceFailureSchema = z13.object({
5080
5119
  summary: z13.string(),
@@ -44691,7 +44730,7 @@ var listCommand13 = defineCommand121({
44691
44730
  });
44692
44731
  registerSchema({
44693
44732
  command: "chats.view",
44694
- description: "Inspect one Session's FULL picture of what it changed \u2014 the unified `effects`: git content (landings, creatives, flows, knowledge, brand), plus DB-only effects that never touch the repo \u2014 Actions, Scheduled Actions, Tags, Tag Manager, Google Analytics, and ad-platform writes \u2014 each resolved to real detail (names, descriptions, priorities, tag types, ad operations). Also `publish` (what each external surface actually did, with the provider's own error), `activity` (the chat's own timeline: status changes, publish start/fail, workspace recoveries, timeouts), `usage` (per-thread cost and the Session's token totals), the kickoff (how it was asked), threads, and commits. Effects are `staged` (in-progress draft) or applied. A completed Session is NOT proof its external changes landed \u2014 read `publish`. Use after `baker chats list` to decide whether to reuse it. Read-only.",
44733
+ description: "Inspect one Session's FULL picture of what it changed \u2014 the unified `effects`: git content (landings, creatives, flows, knowledge, brand), plus DB-only effects that never touch the repo \u2014 Actions, Scheduled Actions, Tags, Tag Manager, Google Analytics, ad-platform writes, the funnel (`funnel`: which steps it added, changed or removed, and which ways in it added or removed in `triggersAdded`/`triggersRemoved`), what counts as a conversion (`conversions`), conversion sends, event sources, and every other staged or already-applied change (`otherChanges`: A/B tests, recipes, library images) \u2014 each resolved to real detail (names, descriptions, priorities, tag types, ad operations) and, once published, its `outcome`. Also `publish` (what each external surface actually did, with the provider's own error), `activity` (the chat's own timeline: status changes, publish start/fail, workspace recoveries, timeouts), `usage` (per-thread cost and the Session's token totals), the kickoff (how it was asked), threads, and commits. Effects are `staged` (in-progress draft) or applied. A completed Session is NOT proof its external changes landed \u2014 read `publish`. Use after `baker chats list` to decide whether to reuse it. Read-only.",
44695
44734
  args: {
44696
44735
  id: { type: "positional", description: "The Session id (from `baker chats list`)", required: true },
44697
44736
  full: {