[boluxx123]

Overview

This PR removes the duplicated fetch/loading/error/empty-state scaffolding shared by the Activity and Incoming pages by extracting a reusable useAsyncPageData-style hook, and migrates both pages to use it. A small follow-up fix was also needed in the dashboard calendar page.

Related Issue

Changes

🔁 Shared Async Page Hook

• [ADD] frontend/src/hooks/useAsyncPageData.ts
  • Encapsulates the common fetch/loading/error/empty-state flow used by both pages.
  • Exposes loading, error, and empty state so pages can render consistent UI without re-implementing the same branching logic.

📄 Page Migrations

• [MODIFY] frontend/src/app/activity/activity-content.tsx

  • Replaced the page-local fetch/loading/error/empty scaffolding with useAsyncPageData.

• [MODIFY] frontend/src/app/incoming/incoming-content.tsx

  • Replaced the page-local fetch/loading/error/empty scaffolding with useAsyncPageData.

• [MODIFY] frontend/src/app/dashboard/calendar/page.tsx

  • Adjusted the page to align with the shared hook's loading/error handling so behavior stays consistent.

Verification Results

npm test -- frontend/src/app/activity frontend/src/app/incoming
✅ Existing tests for both pages pass

Acceptance Criteria	Status
Extract a shared useAsyncPageData-style hook or shared presentational wrapper for loading/error/empty states	✅ Added frontend/src/hooks/useAsyncPageData.ts
Migrate both pages to use it	✅ activity-content.tsx and incoming-content.tsx now use the shared hook
Confirm existing tests for both pages still pass	✅ Existing tests for both pages pass

Closes #1085