fix: persist condensing API configuration in Context Management settings #8873
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

Description
This PR fixes an issue where the condensing API configuration dropdown was not visible in the Context Management settings, causing the selection to reset to "Global Default (all profiles)" after navigating away.
Problem
As reported in #8871:
Solution
Technical Details
The backend already had full support for using the selected condensing API configuration (verified in lines 1006-1081). The issue was purely in the UI layer where the dropdown was missing from the Context Management settings component.
Testing
Fixes #8871
Important
Fixes visibility and persistence of condensing API configuration dropdown in Context Management settings.
ContextManagementSettings.tsx.SettingsView.tsxto passcondensingApiConfigIdprop toContextManagementSettings.ContextManagementSettings.spec.tsxto include tests for the new dropdown and its visibility.This description was created by
for bcbcd20. You can customize this summary. It will automatically update as commits are pushed.