The way I understand this, when the agent runs `bd onboard` at startup, it gets the instructions from beads, which might refer to data files in the beads directory. Keeping them in sync via a separate branch would be an unnecessary overhead. Right?
>>wowami+(OP)
I don't see it as extra overhead - it just changes the git one-liner they use to push and pull their issue tracking content by a few characters.
I like the idea of keeping potentially noisy changes out of my main branch history, since I look at that all the time.
>>simonw+01
You are right. I dug through the document some more. The setup, as mentioned for protected branches [1], should ideally work without much overhead. It does suggest merging back to main, but the FAQ also mentions that the frequency can be decided individually.