docs: Added comprehensive Troubleshooting & Local Setup Failsafe guide to README

[DeepeshKafalatiya]

Description

This PR introduces an actionable "Troubleshooting & Local Setup Failsafe" section to the bottom of the root README.md. It provides incoming contributors with quick, deterministic workarounds for common environments blockers related to Vite 6 module caching, strict Node dependency trees, environment configurations, and conflicting background terminal ports.

Related Issues

Closes #425

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

How Has This Been Tested?

The Markdown document structure has been fully checked for correct blockquote layout, layout cleanliness, and proper formatting highlighting in Markdown preview.

Checklist

• My code follows the code style of this project.
• I have performed a self-review of my own code.
• My changes generate no new warnings.

---

Contributing under GSSoC 2026! Please review and merge. Thank you!

[DeepeshKafalatiya]

Hi Maintainers,
@utksh1

I have successfully added a comprehensive "Troubleshooting & Local Setup Failsafe" section to the root README.md file.

This guide provides explicit, actionable solutions for incoming developers facing common environment roadblocks under Vite 6, such as stale module caching, strict Node dependency tree conflicts, missing .env paths, and occupied terminal background ports.

Please review and merge this under GSSoC 2026! Thank you! 🚀

[utksh1]

Thanks for the docs contribution. This cannot merge in the current form because the added README section has broken Markdown: multiple fenced code blocks are opened and never closed, headings like ###3/###4 are malformed, and the Windows/Linux fence labels are nested incorrectly. Please close every ``` block, normalize the headings, wrap .env and commands in backticks, and keep the wording professional/factual.

[utksh1]

The markdown issues from the previous review are fixed now. The troubleshooting section is properly fenced and the branch is current with passing CI.