Add a global not-found illustration and quick-links to recover from dead routes

[mikewheeleer]

Enrich the not-found page with recovery links

Description

src/app/not-found.tsx renders a minimal 404 message, but a user who hits a dead route gets no obvious way back into the app beyond the browser back button — there are no quick-links to the primary surfaces (Home, Services, Stats, Docs). This issue turns the 404 into a useful recovery page with a labelled navigation list, reusing only routes that exist.

Requirements and context

• Repository scope: Agentpay-Org/Agentpay-frontend only.
• Add a <nav aria-label="Helpful links"> with <Link>s to existing routes (Home, Services, Stats, Docs) below the 404 message.
• Keep the main landmark, the existing heading/copy, the metadata title, and dark-mode classes.
• Only link routes that actually exist under src/app/; do not invent destinations.
• Do not change the not-found behaviour itself (still returned for unmatched routes).

Suggested execution

• Fork the repo and create a branch
• git checkout -b enhancement/error-pages-not-found-links
• Implement changes
  • Write code in: src/app/not-found.tsx.
  • Write comprehensive tests in: create src/app/not-found.test.tsx — assert the heading and the recovery nav with its links render.
  • Add documentation: note the recovery links in README.md.
  • Validate the nav landmark is reachable and the list is semantic.
• Test and commit

Test and commit

• Run npm run lint, npm run typecheck, npm test, and npm run build.
• Cover edge cases: every link resolves and keyboard reachability.
• Include the npm test output.

Example commit message

feat(error-pages): add recovery quick-links to the not-found page

Guidelines

• Minimum 95 percent test coverage for the changed page.
• Clear, reviewer-focused documentation.
• Timeframe: 96 hours.

Community & contribution rewards

• 💬 Join the AgentPay community on Discord for questions, reviews, and faster merges: https://discord.gg/eXvRKkgcv
• ⭐ This is a GrantFox OSS / Official Campaign task and may be rewarded. When your PR is merged you'll be prompted to rate the project — if this issue and the maintainers helped you ship, we'd be grateful for a 5-star rating. Clear questions in Discord and tidy, well-tested PRs are the fastest path to a merge and a reward.

[gloskull]

Hello, I have 4 years of experience delivering solutions for projects like this, covering backend, frontend, and smart contract development. After carefully reviewing your requirements, I have a clear understanding of the task and am confident in my ability to deliver a clean, efficient, and thoroughly tested solution on time. I prioritize code quality, maintainability, and industry best practices throughout the development process.
My PR will be submitted in under 10hours.

[Unclebaffa]

Hello Maintainer,
I'm interested in contributing to this amazing project of yours, I'm confident i will deliver the best result that aligns with this project.
Kindly assign me.
Thank you

[grantfox-oss]

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

Next steps:

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

Good luck! Track your progress on GrantFox.