docs: expand troubleshooting guide section in main README

[Rish-2006]

Closes #732

Summary by CodeRabbit

• Documentation
  • Added a new Troubleshooting section with guidance for resolving build cache and dependency synchronization issues that may cause runtime rendering problems or stale execution logs when working across packages.

[coderabbitai]

📝 Walkthrough

Walkthrough

The README gains a new Troubleshooting section that documents how to resolve build cache and dependency synchronization issues in the monorepo by running bun run clean followed by bun install to fix stale execution logs or rendering problems.

Changes

Troubleshooting Documentation

Layer / File(s)	Summary
Troubleshooting guide expansion README.md	New Troubleshooting subsection added with remediation guidance for build cache conflicts and dependency synchronization issues using bun run clean and bun install commands.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• Karanjot786/TermUI#636: Both PRs modify README.md to add/expand Bun-related contributor setup instructions (Troubleshooting/build cache vs installation prerequisites), directly related at the documentation level.

Suggested labels

type:docs, level:beginner, quality:clean

Suggested reviewers

• Karanjot786

Poem

🐰 A hop, a skip through cache despair,
Now troubleshooters find relief right there,
With bun run clean to clear the way,
Fresh installs bloom—no more delay! 🌿

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The PR description is minimal but includes the required issue link. However, it omits most template sections including package selection, change type, and verification checklist.	Add required template sections: specify which package, select the 'Docs' change type, and complete the verification checklist items.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately reflects the main change: expanding the troubleshooting guide section in the README with clear, specific terminology.
Linked Issues check	✅ Passed	The PR addresses the linked issue #732 by adding a Troubleshooting section covering build cache and dependency synchronization issues as requested.
Out of Scope Changes check	✅ Passed	The PR contains only README documentation changes directly aligned with the linked issue objectives; no unrelated code or refactoring is present.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@README.md`:
- Around line 468-471: Update the README.md near the bash snippet containing
"bun run clean" / "bun install" to explicitly state that "bun install" must be
run from the monorepo root (not from inside a package) to ensure dependency
sync; add a one-line note either above the code block or as an inline comment in
the block clarifying "Run `bun install` from the repo root, never from inside a
package." so contributors know where to execute the commands.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 6f714db3-cc7c-4fe3-916e-6f38dd6c2d2a

📥 Commits

Reviewing files that changed from the base of the PR and between f90f75c and d277911.

📒 Files selected for processing (1)

• README.md

[coderabbitai]

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Specify that bun install must be run from the repository root.

Please add a short note here (or inline in the code block) that this command sequence must be executed from the monorepo root, otherwise dependency sync may still fail for contributors running it inside a package.

Based on learnings: “Run bun install from the repo root, never from inside a package.”

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@README.md` around lines 468 - 471, Update the README.md near the bash snippet
containing "bun run clean" / "bun install" to explicitly state that "bun
install" must be run from the monorepo root (not from inside a package) to
ensure dependency sync; add a one-line note either above the code block or as an
inline comment in the block clarifying "Run `bun install` from the repo root,
never from inside a package." so contributors know where to execute the
commands.