src/components/notifications/NotificationCenter.tsx (1)

27-35: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Consider adding refetchOnWindowFocus to the notifications list query for consistency.

Only unreadCountQuery (line 33) enables refetchOnWindowFocus, but notificationsQuery (lines 27-30) does not. This creates a brief inconsistency window: when the user returns to the tab, the badge count updates immediately but the notifications list remains stale until the next polling interval. While both queries use refetchInterval for eventual consistency, users might see a mismatch between the badge number and the visible list.

🔄 Proposed fix to align refetch behavior

 const notificationsQuery = api.notifications.get.useQuery(
   { limit: 10, offset: 0 },
-  { enabled: !!user, refetchInterval: POLLING_INTERVALS.NOTIFICATIONS },
+  { 
+    enabled: !!user, 
+    refetchOnWindowFocus: true,
+    refetchInterval: POLLING_INTERVALS.NOTIFICATIONS 
+  },
 )

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/components/notifications/NotificationCenter.tsx` around lines 27 - 35,
The notifications list query (notificationsQuery created via
api.notifications.get.useQuery) lacks refetchOnWindowFocus while
unreadCountQuery includes it, causing badge/list inconsistencies; update
notificationsQuery's options to include refetchOnWindowFocus: true (alongside
enabled and refetchInterval) so both queries refresh when the window regains
focus and stay consistent with unreadCountQuery.

src/app/listings/ListingsPage.tsx (1)

68-95: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Avoid showing role-based UI from stale users.me data after sign-out

src/app/listings/ListingsPage.tsx gates the api.users.me query with enabled: isSignedIn === true, but the render logic still uses userQuery.data directly (e.g., {userQuery.data && ...}), and there’s no app-side sign-out handler found that invalidates/clears users.me on auth transitions. Gate those UI checks with isSignedIn (or invalidate users.me on sign-out) so signed-out views can’t temporarily use cached role data.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/app/listings/ListingsPage.tsx` around lines 68 - 95, The page currently
reads userQuery.data directly which can be stale after sign-out; update render
and logic to always gate role-sensitive UI with isSignedIn (e.g., use
"isSignedIn && userQuery.data" instead of "userQuery.data") or, alternatively,
ensure users.me is cleared on sign-out by invalidating/removing the query via
the react-query/queryClient when sign-out occurs; target the
api.users.me.useQuery/userQuery and any places that reference userQuery.data
(and userPreferencesQuery) so role-based UI only renders when isSignedIn is true
or the query is explicitly cleared.