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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@flamingo-stack/openframe-frontend-core",
-  "version": "0.0.217-snapshot.20260601003634",
+  "version": "0.0.217",
   "description": "Shared design system and components for all Flamingo platforms",
   "type": "module",
   "main": "./dist/index.js",

package/src/components/tickets/hooks/use-ticket-engagements.ts

@@ -88,18 +88,13 @@ export function useTicketEngagements(
   const identity = useChatIdentity()
   const identityKey = identity.user?.email ?? 'anon'
 
-  // "Will this ticket fetch its timeline once identity is ready?" — i.e. it's a
-  // real, non-optimistic ticket the caller enabled. INDEPENDENT of whether
-  // identity has resolved yet, so the loading state is correct from the very
-  // first render (before `useChatIdentity` settles).
-  const fetchable =
+  const queryEnabled =
     enabled &&
+    identity.authTier !== 'anon' &&
+    !!identity.user?.email &&
     !!externalTicketId &&
     !externalTicketId.startsWith('temp-') // optimistic placeholders have no real id yet
 
-  const queryEnabled =
-    fetchable && identity.authTier !== 'anon' && !!identity.user?.email
-
   const query = useQuery({
     queryKey: ['ticket-engagements', externalTicketId, identityKey],
     enabled: queryEnabled,
@@ -131,22 +126,7 @@ export function useTicketEngagements(
 
   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 === undefined)),
+    isLoading: queryEnabled && query.isLoading,
     isFetching: query.isFetching,
     error: (query.error as Error | null) ?? null,
     refetch: () => {