Squad undid its own uncommited changes from a previous session #86

Here was my scenario, working in Copilot CLI after having just installed Squad

1. I asked it to do some frontend work. It did it, result seemed fine to me when it finished. It did not automatically try to commit the changes at the end. I didn't commit them either, because...
2. ... I wanted some more UI changes. So I asked for some more. The squad member ran into some issues and so it decided to undo the work that member had done so far. It did so by doing a git checkout... which went back to the last commit and undid the work in step 1 AND the work in step 2.

(note this was in the same copilot cli session and just back to back prompts, essentially)

To its credit, it recovered well eventually (had some of the original work still in context, added some memories or instructions or something to make sure it committed in the future, etc). But it feels like that should be part of the instructions somewhere (if its not already - I recognize its possible the model just ignored instructions).