Missing Checkpoint after adding additional Context

[TonyCollett]

Once a processed task finishes (where we get green text), we should have one final Checkpoint at that point.

For example, once Roo has used the [attempt_completion] tool and given us the green summary text, we as users might submit a follow up, like if there is an error on testing that specific task implementation we might say in that task '@Terminal is displaying this error, can you fix it'

The next Checkpoint is after the first request and response which is usually 'Roo wants to edit this file'

If we want to undo, the checkpoint is either after the edit, or before the green text completion, which means that it will generally reattempt to provide [attempt_completion] again, chewing up additional tokens and regenerating the green text.

Clicking the trash can on the user message only deletes the task content, doesn't revert code to that point.

Workaround is mainly to just commit the code at that completion point to your own repository, but there are times that I don't do that because I don't like to commit code that is 'broken' (causes obvious errors) so I'll often not do that and continue the task only for it to not work or my prompt wasn't clear enough about what to fix.