Context limit and pruning updates

[RomneyDa]

Description

Builds on @Jazzcort's work to make context status more visible to the user

• Small context indicator next to enter button for >50% context filled
• Tooltip shows percentage, newsession option
• turns red when pruning is happening

---

Summary by cubic

Improved context limit handling by updating pruning logic and adding clearer UI feedback when chat history exceeds model limits.

• UI Updates
  • Added a context status indicator showing how full the context window is and when pruning occurs.
  • Replaced old warning messages with a simpler inline error for out-of-context inputs.
• Core Changes
  • Switched to a boolean didPrune and percentage-based context tracking instead of status strings.
  • Updated Redux state and thunks to support new context and pruning indicators.

[github-actions]

⚠️ Conventional Commit Format

Your latest commit message doesn't follow the conventional commit format, but this won't block your PR from being merged. We recommend downloading this extension if you are using VS Code.

Expected Format:

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Examples:

• feat: add changelog generation support
• fix: resolve login redirect issue
• docs: update README with new instructions
• chore: update dependencies

Valid Types:

feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert

This helps with:

• 📝 Automatic changelog generation
• 🚀 Automated semantic versioning
• 📊 Better project history tracking

This is a non-blocking warning - your PR can still be merged without fixing this.

[cubic-dev-ai]

cubic found 1 issue across 10 files. Review it in cubic.dev

_{React with 👍 or 👎 to teach cubic. Tag @cubic-dev-ai to give specific feedback.}

[chezsmithy]

@RomneyDa perfect. Great minds!

[Jazzcort]

@RomneyDa Looking great! Thanks for cleaning up some mess I left in #4816. 😁