Summary

Implement a complete notification experience for both public/anonymous users and authenticated users after login.

Bounty

• Reward: 3000 MRG
• Bounty type: feature bounty
• Area: notifications, public UI, authenticated dashboard

Scope

Build a coherent notification system across the app. Public/anonymous pages should have polished status/toast notifications for user actions and errors. Logged-in users should have an authenticated notification experience in the dashboard, including a notification entry point and notification list/center.

Expected Behavior

Public/outside-login experience:

• User actions show clear toast/status notifications where appropriate.
• Errors and success states are readable, non-overlapping, and responsive.
• Notifications do not cover important CTAs or break mobile layouts.
• Notification styling matches the existing MergeOS design system.

Authenticated/dashboard experience:

• Logged-in users can access notifications from the dashboard/navigation/profile area.
• Notification list shows useful fields such as subject/title, body/summary, channel/status, project reference when available, and created time.
• Unread/read or new/seen state is represented if supported by existing backend data; otherwise document the limitation.
• Empty, loading, and error states are handled cleanly.
• Notifications remain usable across dashboard, project, payment, marketplace, and ledger contexts.

Acceptance Criteria

• Add or fix notification UI for public/outside-login pages and logged-in dashboard users.
• Reuse existing backend notification data/API patterns where available instead of hardcoding static-only UI.
• Verify after login by opening the dashboard and viewing notifications.
• Verify anonymous/public notification behavior without login.
• Verify at least these viewports: 1366x900, 768x900, 430x900, 390x664, 360x640.
• Include before/after screenshots or a short video/GIF showing public notifications and authenticated dashboard notifications.
• Include test/build output, at minimum npm test and npm run build:local for the frontend.
• If backend/API changes are required, include relevant Go tests or explain the test gap.
• Note whether test data came from real backend notifications, local state, seed data, mocked data, or empty-state testing.

Non-Goals

• Do not redesign the entire dashboard unrelated to notifications.
• Do not introduce external push notification providers unless clearly necessary and documented.
• Do not expose private customer data in public notifications.

Claim Requirement

Before opening a PR, star this repository and claim the bounty in the Claim Token issue. Link the claim comment in the PR.