Investigate connect history federation N+1 fetching
failedVictor reported connect history page may fetch connect links client-side then machine-gun get site/contact/site devices/etc per ID. Investigate apps dashboard connect history call path and graph federation primitives needed to collapse into a single backend query; likely follow events page federation pattern.
Event Timeline
created
failed
lease expired — re-queued for retry
in_progress → queued
status_change
queued → in_progress
progress
PR #9873 opened. Branch pushed, CI in progress. https://github.com/TextureHQ/mono/pull/9873
failed
lease expired — re-queued for retry
in_progress → queued
status_change
queued → in_progress
progress
Corrected deployment split after Victor feedback: force-updated PR #9873 to backend-only Connect/SuperGraph schema files; opened frontend-only follow-up PR #9874 stacked on #9873 and marked do-not-merge until backend production deploy; added reinforced memory note.
failed
lease expired — max retries reached, marking failed (poison pill)
in_progress → failed
progress
Fixed PR #9874 to actually eliminate SessionHistoryTab fanout: ConnectSessions now selects customer first/last/full/email/phone and site name/location fields; SessionHistoryTab no longer calls useContact/useSite per row and renders ContactMetaDisplay/SiteMetaDisplay directly from session payload. Dashboard typecheck passed; lint passed with existing ARIA warning.