feat(ui): implement graceful error boundary for project loader

[Shashank-8p]

📝 Description

Resolves an issue where missing or crashing project modules resulted in silent front-end failures.

Architectural Changes Implemented:

• Error Boundaries: Wrapped the dynamic module execution window[fnName]() in a strict try-catch block.
• Fallback UI: If a module fails to load or crashes during execution, the application now catches the exception and renders a styled "SYSTEM ERROR: PROJECT OFFLINE" state with an actionable "Retry Connection" button, instead of leaving the user with a broken interface.

🔗 Linked Issue

Closes #806

---

📋 Contribution Checklist

• My code strictly adheres to the project guidelines.
• I have tested the error boundary locally by attempting to load a non-existent project.
• GSSoC 2026: I have been formally assigned to this issue and noted it above.

[vercel]

@Shashank-8p is attempting to deploy a commit to the Anuj's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

🎉 Thank you for your contribution!

Your Pull Request has been merged successfully.

We appreciate the time and effort you put into improving this project. Contributions like yours help the repository grow and stay useful for everyone.

If you'd like to contribute again, please check the open issues and make sure you are assigned before opening another Pull Request.

Thanks again for your support! 🙌