@flamingo-stack/openframe-frontend-core 0.0.217-snapshot.20260601003634 → 0.0.217

package/dist/components/tickets/index.js

@@ -237,8 +237,7 @@ var LIST_ENGAGEMENTS_ENDPOINT = "/api/chat/agent/list-engagements";
 function useTicketEngagements(externalTicketId, enabled = true, refetchInterval = false) {
   const identity = useChatIdentity();
   const identityKey = identity.user?.email ?? "anon";
-  const fetchable = enabled && !!externalTicketId && !externalTicketId.startsWith("temp-");
-  const queryEnabled = fetchable && identity.authTier !== "anon" && !!identity.user?.email;
+  const queryEnabled = enabled && identity.authTier !== "anon" && !!identity.user?.email && !!externalTicketId && !externalTicketId.startsWith("temp-");
   const query = useQuery({
     queryKey: ["ticket-engagements", externalTicketId, identityKey],
     enabled: queryEnabled,
@@ -269,20 +268,7 @@ function useTicketEngagements(externalTicketId, enabled = true, refetchInterval
   });
   return {
     engagements: query.data ?? [],
-    // Loading-state truth that prevents the "body → blink → skeleton → data"
-    // double-flash. The bug: `useChatIdentity` starts at anon defaults and
-    // resolves async, so on the first render `queryEnabled` is false and the
-    // OLD `queryEnabled && query.isLoading` returned FALSE — the panel rendered
-    // the ticket body, THEN identity resolved, the query enabled, isLoading
-    // flipped true → skeleton appeared (the blink), then data landed.
-    //
-    // Fix: for a fetchable ticket we are "loading" whenever we don't yet have
-    // the timeline to show — that includes the window while identity is still
-    // resolving (so we skeleton from the FIRST render, never the body) AND the
-    // cold query fetch (`data === undefined`). A background poll keeps
-    // `query.data` defined, so it never re-flashes the skeleton. Non-fetchable
-    // (optimistic/disabled) or a resolved-anon viewer → not loading.
-    isLoading: fetchable && (identity.isLoading || queryEnabled && query.data === void 0),
+    isLoading: queryEnabled && query.isLoading,
     isFetching: query.isFetching,
     error: query.error ?? null,
     refetch: () => {