Harden real-time marketplace provider lifecycle and reconnect semantics

[grantfox-oss]

mprove lifecycle management for realtime marketplace updates so disconnects, reconnects, and stale subscriptions cannot leave stale data or duplicated listeners behind.

• Affected files: app/frontend/src/hooks/providers/productionRealtimeProvider.ts, app/frontend/src/hooks/providers/mockMarketplaceProvider.ts, app/frontend/src/components/NotificationCenterProvider.tsx, app/frontend/src/components/NotificationFeed.tsx, app/frontend/src/app/marketplace/page.tsx, app/frontend/src/app/notifications/page.tsx, app/frontend/src/lib/errorReporter.ts, app/frontend/src/hooks/useMarketData.ts
• Acceptance criteria:
  • Realtime subscriptions cleanly unsubscribe and reconnect without duplicated listeners or stale updates.
  • Disconnected or failed connections recover without leaving dead event handlers.
  • Realtime provider failures are surfaced in error telemetry and user-visible UI states.

[Violetlove200100]

I would like to work on this issue by improving the real-time marketplace provider lifecycle and reconnect behavior. I will handle connection, disconnection, and retry scenarios reliably, while adding tests to ensure stable behavior during network interruptions and reconnections.

[kimanicode]

I have experience building realtime WebSocket/SSE systems with proper lifecycle management cleanup, reconnection backoff, and preventing duplicate subscriptions. I've reviewed the affected files and understand the scope. I can submit a PR within 2–3 days.

[grantfox-oss]

🦊 GrantFox — @Violetlove200100 has been assigned to this issue as part of the Third Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #526)
2. Your PR will be reviewed by the BlockDash-Studios maintainers

Good luck! Track your progress on GrantFox.