[ENHANCEMENT] Create checkpoints before compressing the context

[jwadow]

Problem (one or two sentences)

Context compression is a fairly critical step, which can be done automatically, among other things. Reversing this process requires losing a few messages.

Context (who is affected and when)

This affects those who don't want to waste time and effort rolling back and losing some of their most recent messages. It's much easier to create a checkpoint right before the compression.

Desired behavior (conceptual, not technical)

Before any context compression (manual or automatic), create a checkpoint.

Constraints / preferences (optional)

No response

Request checklist

• I've searched existing Issues and Discussions for duplicates
• This describes a specific problem with clear context and impact

Roo Code Task Links (optional)

No response

Acceptance criteria (optional)

No response

Proposed approach (optional)

No response

Trade-offs / risks (optional)

No response

[roomote]

I'm exploring a potential fix for automatically creating checkpoints before context compression. I'll open a PR to share progress on this enhancement.

[roomote]

Opened PR #9335 with my attempt at addressing this issue. The implementation automatically creates checkpoints before both manual and automatic context compression operations, allowing users to revert if needed. Feedback welcome!

[hannesrudolph]

@roomote create a visable checkpoint before each context-management event.

[roomote]

I've seen your comment and will work on creating visible checkpoints before context-management events. The previous implementation used suppressMessage=true which hid the checkpoint - I'll update this to make checkpoints visible. I'll open a PR to share progress.