Always put planning docs in the main/master branch?

[ThePaulius]

End of day brain dump:

I use branches, worktrees, multiple computers and other devs also join in to do stuff.

Very often we work on the same thing, either re-discussing, planning or executing the same phase.

This is because planning docs get put in branches with the code, so when someone else jumps in, it's not in main and gsd-progress or the gsd-manager doesn't see it.

Can we do something here? Like can gsd-pause-work know to cherry-pick docs to main, and reference the feature branch for a new session on a new machine, push the branch and write the handover etc?