History check point

Your idea

Ability to mark a a history entry as a check point for easy reference.

Problem to be solved

Often times while composing you'd go on a tangent to try out some little idea(s) that may or may not work and you'd end up undoing many steps and trying to guess the point at which the original score state was before testing out the new idea.

It would be very helpful if we could pin down a history checkpoint to organize the forementioned workflow.

It would also be SUPER COOL if checkpoints could be stored within the file and loaded each time it is opened. This would sort of be like saving different verrsions of the score.

Prior art

No response

Additional context

No response

Checklist

• This request follows the guidelines for reporting issues
• I have verified that this feature request has not been logged before, by searching the issue tracker for similar requests

Start by locating MuseScore's history or undo/redo implementation; the issue names no files, tests, or entry points. Define the checkpoint behavior, including whether checkpoints persist in score files, before identifying implementation and test locations.