fixed profile context condensation threshold

[PaperBoardOfficial]

Related GitHub Issue

Closes: #5229

Description

The issue occurred because the currentProfileId was using the provider model name not the id of the provider. Hence, it always picked the "default" context condensing threshold. Now, it correctly picks the right currentProfileId.

Test Procedure

Pre-Submission Checklist

• Issue Linked: This PR is linked to an approved GitHub Issue (see "Related GitHub Issue" above).
• Scope: My changes are focused on the linked issue (one major feature/fix per PR).
• Self-Review: I have performed a thorough self-review of my code.
• Testing: New and/or updated tests have been added to cover my changes (if applicable).
• Documentation Impact: I have considered if my changes require documentation updates (see "Documentation Updates" section below).
• Contribution Guidelines: I have read and agree to the Contributor Guidelines.

Screenshots / Videos

Documentation Updates

Additional Notes

Get in Touch

---

Important

Fixes currentProfileId usage in Task.ts to ensure correct context condensing threshold by using provider ID instead of model name.

• Behavior:
  • Fixes currentProfileId usage in Task.ts by using the provider ID instead of the model name.
  • Ensures correct context condensing threshold is applied in truncateConversationIfNeeded().
• Misc:
  • Updates currentProfileId logic in attemptApiRequest() to match the fix.

^{This description was created by for 49ef16e. You can customize this summary. It will automatically update as commits are pushed.}

[daniel-lxs]

Thank you for the fix @PaperBoardOfficial