@koda-sl/baker-cli 0.273.0 → 0.274.0-dev.bbba3d7fc

package/dist/cli.js

@@ -58,7 +58,7 @@ import {
   ulid,
   validateCanvasDeep,
   ytDlpBlockSignal
-} from "./chunk-36KVUYVL.js";
+} from "./chunk-VWLNPPC6.js";
 import {
   csvOrJson,
   daysAgoIso,
@@ -12459,7 +12459,22 @@ var ANALYTICS_EVENT_TYPES = [
    * know who this was" unanswerable.
    */
   "identify",
-  /** Escape hatch for a page-specific event. */
+  /**
+   * A named event: an escape hatch a page defines, or one a client's own server
+   * posted to `POST /v1/events`.
+   *
+   * One type for both, deliberately. There was briefly a `server_event`, and
+   * the type was the mistake: every report that shows named events whitelists
+   * `custom`, so a server-sent "Deal won" was structurally invisible on the
+   * Page events card, in Top pages and in the events catalogue — the three
+   * screens somebody would look at after being told it had arrived. GA4 makes
+   * the same call for the same reason: a Measurement Protocol event is just an
+   * event, and the transport is a property.
+   *
+   * Which collector wrote it is {@link ANALYTICS_SOURCES} — `client` for a
+   * page, `ingest` for a third party's server — and every report that needs to
+   * tell them apart filters on that.
+   */
   "custom"
 ];
 var ANALYTICS_DEVICE_TYPES = ["desktop", "mobile", "tablet", "bot", "unknown"];
@@ -12982,6 +12997,19 @@ var analyticsQueryRequestSchema = z25.object({
    * superset and the right default for "how is paid doing".
    */
   adPlatform: z25.enum(AD_PLATFORMS).optional(),
+  /**
+   * Read only what one collector produced: `site` for everything Baker
+   * measured itself, `systems` for what a client's own server posted to
+   * `POST /v1/events`.
+   *
+   * Omit it for all of it, which is the default and the honest superset.
+   * Only the reads where the split is a question somebody asks honour it —
+   * the totals, the trend, the two page-event reads, the conversion
+   * breakdown and the events catalogue. A session-scoped report cannot: an
+   * ingest row carries no `session_id`, deliberately, so there is no visit
+   * for it to be counted in.
+   */
+  eventOrigin: z25.enum(["site", "systems"]).optional(),
   /** Return the long breakdowns and the per-day trend. */
   full: z25.boolean().optional(),
   /**
@@ -13254,6 +13282,7 @@ var analyticsTagRowSchema = z25.object({
   /** Converting visits per entrance. */
   conversionRate: z25.number().min(0).max(1).nullable()
 });
+var ANALYTICS_EVENT_ORIGINS = ["site", "systems", "both"];
 var analyticsCustomEventRowSchema = z25.object({
   eventName: z25.string(),
   events: z25.number().int().nonnegative(),
@@ -13269,7 +13298,9 @@ var analyticsCustomEventRowSchema = z25.object({
    */
   propertyKeys: z25.array(z25.string()),
   valueTotal: z25.number(),
-  landings: z25.array(z25.string())
+  landings: z25.array(z25.string()),
+  /** Which collector produced this name — and `both` when more than one did. */
+  origin: z25.enum(ANALYTICS_EVENT_ORIGINS)
 });
 var analyticsEventBreakdownRowSchema = z25.object({
   value: z25.string(),
@@ -13604,6 +13635,16 @@ var analyticsConversionRowSchema = z25.object({
 var analyticsEventCatalogRowSchema = z25.object({
   /** `form:…` | `submit:…` | `page:…` | `exit:…` — parse with `parseEventKey`. */
   eventKey: z25.string(),
+  /**
+   * Which collector produced this key — and `both` when more than one did.
+   *
+   * On the row rather than in the key, which is the whole shape of the change
+   * that removed the `server:` family: a picker can say where an event came
+   * from without a filter round-trip, and a report can still separate the two
+   * populations at any grain, but nothing downstream has to learn a second
+   * vocabulary to count one.
+   */
+  origin: z25.enum(ANALYTICS_EVENT_ORIGINS),
   events: z25.number(),
   sessions: z25.number(),
   /** The Form node's kind, for a `form:` key. Empty otherwise. */