feat: Add checkpoint after every message (#5995)

[roomote]

Summary

This PR implements automatic checkpoints after every message exchange, as requested in issue #5995.

Changes

• Modified presentAssistantMessage.ts to save checkpoints after every assistant message, not just when files are modified
• Added checkpoint saving in Task.ts after user messages to preserve any manual edits made between messages
• Removed the conditional logic that only saved checkpoints when files were detected as modified

Benefits

• User's manual changes between messages are always preserved
• Provides better recovery points for the conversation history
• Ensures no work is lost if something goes wrong between messages

Testing

• All existing tests pass (2938 tests passing)
• The checkpoint functionality continues to work as before, just more frequently

Fixes #5995

---

Important

Save checkpoints after every message exchange in presentAssistantMessage.ts and Task.ts, ensuring manual edits are preserved and removing conditional logic based on file modifications.

• Behavior:
  • Save checkpoints after every message in presentAssistantMessage.ts and Task.ts, ensuring manual edits are preserved.
  • Removed conditional logic for checkpoint saving based on file modifications in presentAssistantMessage.ts.
• Testing:
  • All existing tests pass (2938 tests passing).
  • Checkpoint functionality remains unchanged, but occurs more frequently.

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

[ellipsis-dev]

A new checkpoint is saved after processing a user message. Please ensure that this call respects the 'enableCheckpoints' flag and consider wrapping 'await checkpointSave(this)' in a try/catch block to log errors rather than interrupting the task flow.

[daniel-lxs]

This should be handled differently, instead of creating a new checkpoint after each message we should simply show the same checkpoint button on all subsequent messages from the point the checkpoint was created.

That way the change only needs to be made in the UI.

[omagoduck]

This should be handled differently, instead of creating a new checkpoint after each message we should simply show the same checkpoint button on all subsequent messages from the point the checkpoint was created.

That way the change only needs to be made in the UI.

Can we have a manual checkpoint option? @daniel-lxs

[mrubens]

This should be handled differently, instead of creating a new checkpoint after each message we should simply show the same checkpoint button on all subsequent messages from the point the checkpoint was created.

That way the change only needs to be made in the UI.

@roomote-agent can you make this change?

[roomote]

Hi @mrubens! I understand the request - instead of creating a new checkpoint after each message, we should show the same checkpoint button on all subsequent messages from the point the checkpoint was created. This would be a UI-only change. Let me investigate the current implementation and make the necessary changes.

[roomote]

Hi @mrubens! I've implemented the requested change in PR #6273.

Instead of creating new checkpoints after each message, the UI now shows the same checkpoint button on all subsequent messages from the point the checkpoint was created. This is a UI-only change as you suggested.

Please take a look and let me know if this meets your requirements!