@koda-sl/baker-cli 0.238.0 → 0.239.0

package/dist/cli.js

@@ -12562,7 +12562,9 @@ var analyticsDimensionRowSchema = z24.object({
 var analyticsFunnelStepSchema = z24.object({
   stepId: z24.string(),
   stepIndex: z24.number().int().nonnegative(),
+  /** Visits that moved forward into this step. Never events — see `visits`. */
   views: z24.number().int().nonnegative(),
+  /** Visits that finished this step and moved on. */
   completions: z24.number().int().nonnegative(),
   /** Share of viewers who did not complete this step, 0–1. */
   dropRate: z24.number().min(0).max(1).nullable(),
@@ -12574,13 +12576,37 @@ var analyticsFunnelStepSchema = z24.object({
    * conversion, and knowing which step owns it is what stops a drop-off chart
    * treating the booking widget's "profile viewed" as a funnel stage.
    */
-  convertedSessions: z24.number().int().nonnegative()
+  convertedSessions: z24.number().int().nonnegative(),
+  /**
+   * This step is where the Form ends — a confirmation screen, not a loss.
+   *
+   * Stated rather than left to be inferred. The dashboard used to read it off
+   * `dropRate === null`, which is also how a step nobody viewed arrives, so a
+   * converting link node in the middle of a Form was labelled its ending.
+   */
+  isEnding: z24.boolean()
 });
 var analyticsFunnelSchema = z24.object({
   flowSlug: z24.string(),
+  /**
+   * Visits that saw the Form at all — the denominator for every share here.
+   *
+   * Read this, not `starts`, whenever the question is "out of how many". A
+   * start is recorded at the visitor's FIRST INTERACTION, so the two differ by
+   * exactly the people who looked at the Form and never touched it — usually
+   * most of them, and always the group a drop-off chart exists to find.
+   *
+   * Every count in this object is distinct visits, including each step's
+   * `views` and `completions`. That is load-bearing rather than incidental:
+   * the screen divides these by each other, and while the steps counted events
+   * a Form four people had opened reported one step reached fifteen times and
+   * fourteen people lost.
+   */
+  visits: z24.number().int().nonnegative(),
+  /** Visits that interacted with the Form at all — typed, picked, or advanced. */
   starts: z24.number().int().nonnegative(),
   submits: z24.number().int().nonnegative(),
-  /** Submits per start, 0–1. */
+  /** Conversions per visit that opened the Form, 0–1. */
   completionRate: z24.number().min(0).max(1).nullable(),
   /** The step losing the most people. The single most useful field here. */
   worstStep: analyticsFunnelStepSchema.nullable(),
@@ -23754,7 +23780,7 @@ var funnelCommand = presetCommand({
 var flowCommand = presetCommand({
   name: "flow",
   preset: "flow",
-  description: "One Form in depth: how many people it converted, where they went between steps, the per-step table, and every trigger it raised. Read `flowSummary.convertedSessions`, not `submits` \u2014 a Form that books a call on a scheduling node in the MIDDLE of the flow never emits a submit, so it reports zero submits and every one of its real bookings as conversions. `flowPaths` is the flow as edges between steps, bracketed by __flow_start__, __flow_converted__ and __flow_exit__, which is how a branching Form is read at all: a per-step table cannot say that of the people who left step two, forty went to the booking branch and ninety went nowhere.",
+  description: "One Form in depth: how many people it converted, where they went between steps, the per-step table, and every trigger it raised. Every count is DISTINCT VISITS, so quote shares against `funnels[].visits` \u2014 the visits that opened the Form \u2014 and never against `starts`, which is only the visits that touched it. The gap between the two is people who read the Form and left, and on most Forms it is the largest loss there is. Read `flowSummary.convertedSessions`, not `submits` \u2014 a Form that books a call on a scheduling node in the MIDDLE of the flow never emits a submit, so it reports zero submits and every one of its real bookings as conversions. `flowPaths` is the flow as edges between steps, bracketed by __flow_start__, __flow_converted__ and __flow_exit__, which is how a branching Form is read at all: a per-step table cannot say that of the people who left step two, forty went to the booking branch and ninety went nowhere.",
   extraArgs: { flow: { type: "string", description: "Form slug (default: every Form)", required: false } },
   resolve: (args) => ({ preset: "flow", flowSlug: args.flow ? String(args.flow) : void 0 })
 });