@syntrologie/adapt-content 2.8.0-canary.573 → 2.8.0-canary.575

package/dist/schema.js

@@ -4406,6 +4406,16 @@ var TELEMETRY_EVENTS = {
     scope: "open",
     props: ["tile_id", "tile_kind", "visible_ms"]
   }),
+  // A tile's own data load finished: the network wait between the concierge
+  // mounting a tile and the shopper seeing its content (BUG-1784767817 was a
+  // 30 s reviews hang here). `outcome` is 'ok' | 'error'; `requested` is how
+  // many items the tile asked for, `received` how many came back.
+  syntro_tile_data_received: entry({
+    subject: "tile_data",
+    verb: "received",
+    scope: "open",
+    props: ["tile_id", "tile_kind", "total_ms", "outcome", "requested", "received"]
+  }),
   // The three chat atoms are OPEN-scope: they carry `surface` / `open_id` and
   // only make sense inside a concierge open. An INLINE chat bar (no concierge)
   // still dispatches them on every turn, and the core drops each one and
@@ -4423,7 +4433,8 @@ var TELEMETRY_EVENTS = {
     subject: "chat_reply",
     verb: "received",
     scope: "open",
-    props: ["turn", "ttft_ms", "total_ms", "mounts", "cards"]
+    // mount_tools: the mount_* tool name of every mount this reply fired, in order (two product cards appear twice).
+    props: ["turn", "ttft_ms", "total_ms", "mounts", "cards", "mount_tools"]
   }),
   syntro_chat_interrupted: entry({
     subject: "chat",