### What problem does this proposed feature solve? When `autoCondenseContext` is triggered or eventually manual condense operations are triggered we should track telemetry around these events. ### Describe the proposed solution in detail The initial PR was implemented here https://github.com/RooVetGit/Roo-Code/pull/3582 When the conversation is summarized we should track telemetry with information about the event ### Technical considerations or implementation details (optional) _No response_ ### Describe alternatives considered (if any) _No response_ ### Additional Context & Mockups _No response_ ### Proposal Checklist - [x] I have searched existing Issues and Discussions to ensure this proposal is not a duplicate. - [x] This proposal is for a specific, actionable change intended for implementation (not a general idea). - [x] I understand that this proposal requires review and approval before any development work begins. ### Are you interested in implementing this feature if approved? - [ ] Yes, I would like to contribute to implementing this feature.
What problem does this proposed feature solve?
When
autoCondenseContextis triggered or eventually manual condense operations are triggered we should track telemetry around these events.Describe the proposed solution in detail
The initial PR was implemented here #3582
When the conversation is summarized we should track telemetry with information about the event
Technical considerations or implementation details (optional)
No response
Describe alternatives considered (if any)
No response
Additional Context & Mockups
No response
Proposal Checklist
Are you interested in implementing this feature if approved?