feat: add Bug Report option & About menu in Settings, fix Windows onboarding path linking

[VariableThe]

Summary of Changes

1. Bug Report Option: Added a Submit a Bug Report button under Settings > System that opens the GitHub Issue creation form ().
2. About Menu: Added an About section at the bottom of Settings displaying the PaperCache logo, dynamic app version (), a check for updates button, Ko-fi support link, and a thank you note.
3. Windows Onboarding & Link Resolution: Fixed an issue on Windows where note IDs generated by file discovery contained backslashes (e.g. onboarding\Editor.md), causing internal Markdown /file links in Welcome.md to fail lookup and generate empty duplicate files. Normalized note IDs across the Rust backend (fs.rs) and TypeScript frontend (useNoteStorage.ts, markdownPlugin.ts, GraphView.tsx) to consistently use forward slashes on all platforms. Updated onboarding file logic to ensure templates regenerate cleanly on app updates.

Verification & Testing

• ✅ Ran npm run lint (passed cleanly with Prettier & ESLint rules applied).
• ✅ Ran npx vitest run (35/35 unit tests passed).
• ✅ Ran npm run build (Vite + TypeScript production bundle generated cleanly).
• ✅ Ran cargo check (Rust backend verified with no errors).

[coderabbitai]

Warning

Review limit reached

@VariableThe, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 9 minutes and 1 second. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more credits in the billing tab to continue.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 4e3dceb7-426e-4cb5-a2fe-54aa2b560b4e

📥 Commits

Reviewing files that changed from the base of the PR and between d99e5b8 and 515e18f.

📒 Files selected for processing (8)

• AUDIT_LOG.md
• CHANGELOG.md
• src-tauri/src/commands/fs.rs
• src/GraphView.tsx
• src/Settings.tsx
• src/hooks/useNoteStorage.ts
• src/lib/editor/markdownPlugin.ts
• src/setupTests.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/settings-bug-report-and-about

---

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.}