[Performance] Add React Error Boundaries around Monaco Editor and AI Chat Panel

[Somil450]

Problem

The playground page (app/playground/[id]/page.tsx) has no React Error Boundary wrapping the Monaco Editor or the AI Chat Panel. If either of these complex third-party components throws an uncaught runtime error, the entire playground page unmounts - the user loses all unsaved work with no recovery path.

Proposed Solution

Create a reusable ErrorBoundary component (or use the react-error-boundary package) and wrap:

<ErrorBoundary fallback={<EditorErrorFallback />}>
  <MonacoEditor ... />
</ErrorBoundary>

<ErrorBoundary fallback={<ChatErrorFallback />}>
  <AIChatPanel ... />
</ErrorBoundary>

Each fallback should:

• Display a user-friendly error message
• • Provide a "Reload component" button that resets the boundary
• • • Log the error to the console

[github-actions]

👋 Thanks for opening an issue, @Somil450!

Our maintainers will review this issue shortly 🚀

---

📘 Before Contributing

Please read the contribution guide carefully before requesting assignment:

👉 https://github.com/piyushdotcomm/Editron/blob/main/CONTRIBUTING.md

---

🏷️ NSoC'26 / GSSoC'26 Requirement

Please clearly mention whether you are contributing via:

• NSoC'26
• GSSoC'26
• or as a regular contributor

Example: I am contributing under GSSoC'26

⚠️ Assignment requests without this information may be rejected automatically.

---

⏳ GSSoC Assignment Restriction

GSSoC contributors will only be allowed to take issue assignments after:

🗓️ May 15th, 12:00 AM IST

Before that date, assignment requests from GSSoC contributors will be automatically blocked.

---

🤖 Assignment System

To request assignment, comment: /assign or assign me

The smart assignment workflow validates:

• contributor eligibility
• NSoC/GSSoC participation mention
• active issue assignment limits
• repository contribution rules

---

⚠️ Important Repository Rules

• Do not start working before assignment
• Maximum 3 active assigned issues per contributor
• Contributors are encouraged to combine related fixes into 1–2 quality PRs instead of many small PRs
• PRs without assignment may be closed
• Spam or low-quality PRs may be rejected

Happy contributing 🎉