Add a reduced-motion guard to the Notification page framer-motion list transitions

[1nonlypiece]

📌 Description

src/pages/Notification.tsx animates list items with framer-motion
(AnimatePresence + transitionEnter) without honouring
prefers-reduced-motion. Users with motion sensitivity see animated entrance on
every page change. This issue gates the animation behind the reduced-motion
preference.

🎯 Requirements and Context

• Read prefers-reduced-motion (reuse the existing hook pattern) and disable or
  shorten transitions when set.
• No layout shift difference between motion and reduced-motion modes.
• Keep the default animated behaviour when motion is allowed.

🛠️ Suggested Execution

1. Fork the repo and create a branch

git checkout -b a11y/notification-reduced-motion

2. Implement changes

• Update src/pages/Notification.tsx (and extract a shared hook if helpful).
• Tests: extend src/pages/__tests__/Notification.test.tsx mocking matchMedia.
• Docs: note the reduced-motion behaviour.

3. Test and commit

• Run npm test.
• Cover edge cases: reduced-motion on/off, matchMedia change mid-session, no
  visual jump.

Example commit message

a11y: respect prefers-reduced-motion in Notification list transitions

✅ Guidelines

• Minimum 95% test coverage on the new/changed lines.
• No layout shift between modes.
• Timeframe: 96 hours.

🏷️ Labels

type-security · area-frontend · type-enhancement · MAYBE REWARDED · GRANTFOX OSS · OFFICIAL CAMPAIGN

💬 Community & Support

• Join the Disciplr contributor Discord to coordinate, ask questions, and get
  unblocked fast: https://discord.gg/xvNAvMJf
• Please introduce yourself in the channel before you start so we can avoid
  duplicate work, pair you with a reviewer, and get your PR merged quickly.
• Maintainers actively triage this channel and aim for fast, clear, respectful
  reviews — reach out any time you're blocked.

[Tekprecious]

@Tekprecious has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I have experience for this and have reviewed the code; I can submit a PR within 24hrs.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Tekprecious to this issue.

[drips-wave]

Congratulations, @Tekprecious! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @Tekprecious: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊