added troubeshooting page, fixed 404 page layout issue and updated fa…

[Sajjad21990]

…vicon

Description

Testing (ignore for documentation update)

Type of change

• Bug fix
• New feature
• Breaking change
• Documentation update

Checklist:

• I have read and agree to the Code of Conduct.
• I have signed the Contributor License Agreement (CLA).
• I have considered the Security Policy.
• I have self-reviewed and tested my code.
• I have updated documentation as needed.
• I agree to the project's custom license.

Additional Notes:

Summary by CodeRabbit

Release Notes

• New Features

  • Added custom 404 error pages with light and dark mode support.

• Documentation

  • Added troubleshooting documentation covering verification flow, SDK version, session management, page loading, request matching, claims, validation, proof, and exceptions.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
docs	Ready	Preview, Comment	Jan 21, 2026 4:03am

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request introduces two new Next.js 404 error page components with light/dark mode support, updates the documentation metadata to include a "troubleshooting" entry, and adds a new troubleshooting documentation file detailing Reclaim Protocol integration event categories and logging guidance.

Changes

Cohort / File(s)	Summary
Error Pages app/(home)/not-found.tsx, app/not-found.tsx	Two new 404 page components with fixed positioning, dark/light mode support, and navigation links to home.
Documentation Metadata content/docs/meta.json	Added "troubleshooting" entry to the pages array in public navigation metadata.
Troubleshooting Guide content/docs/troubleshooting.mdx	New documentation file with 10 event log categories, including tables detailing event types, log levels, and descriptions for Reclaim Protocol integrations.

Estimated Code Review Effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly Related PRs

• added new page #46: Modifies content/docs/meta.json by updating the pages array with a new documentation entry, sharing the same file-level changes.

Suggested Reviewers

• RealAdii

Poem

🐰 A 404 page with flair so bright,
Toggles between the day and night,
Troubleshooting docs take their stance,
Guiding users through protocol's dance! ✨

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title mentions a troubleshooting page and 404 fix, which align with changes in the PR, but is truncated mid-word ('troubeshooting' appears misspelled and 'updated fa…' is cut off).	Complete and correct the title. Use proper spelling (e.g., 'troubleshooting') and ensure the full title is visible without truncation.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@content/docs/troubleshooting.mdx`:
- Around line 25-26: Update the wording for consistency: change occurrences of
"inapp SDK" to "in‑app SDK" and ensure "URL" uses uppercase. Specifically update
the table rows containing `UPDATE_AVAILABLE` and `SDK_OUTDATED` (and the similar
occurrences around lines 39-40) to read "in‑app SDK" and "URL" where applicable
so the casing is consistent across the document.

🧹 Nitpick comments (1)

app/not-found.tsx (1)

1-24: Consider extracting a shared 404 component to avoid drift.

This file duplicates the NotFound markup in app/(home)/not-found.tsx. A shared component would reduce maintenance overhead and keep the two routes consistent.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Minor copy edits for consistency.

Prefer “in-app SDK” and “URL” for standard casing.

✏️ Proposed doc copy fix

-| `UPDATE_AVAILABLE` | WARNING | An update for inapp SDK is available. Use is still allowed. |
-| `SDK_OUTDATED` | ERROR | An update for inapp SDK is available and the current version cannot be used anymore. |
+| `UPDATE_AVAILABLE` | WARNING | An update for in-app SDK is available. Use is still allowed. |
+| `SDK_OUTDATED` | ERROR | An update for in-app SDK is available and the current version cannot be used anymore. |
@@
-| `LOADING_INITIAL_URL` | INFO | Sending request to load initial url. |
+| `LOADING_INITIAL_URL` | INFO | Sending request to load initial URL. |

Also applies to: 39-40

🤖 Prompt for AI Agents

In `@content/docs/troubleshooting.mdx` around lines 25 - 26, Update the wording
for consistency: change occurrences of "inapp SDK" to "in‑app SDK" and ensure
"URL" uses uppercase. Specifically update the table rows containing
`UPDATE_AVAILABLE` and `SDK_OUTDATED` (and the similar occurrences around lines
39-40) to read "in‑app SDK" and "URL" where applicable so the casing is
consistent across the document.