Who gets to touch the repo
Most engineering tools quietly assume everyone using them is already an engineer.
Open almost any tool built for software teams and it assumes, somewhere in its design, that the person using it already knows how to read a diff, resolve a merge conflict, and reason about a build pipeline. That assumption used to be reasonable, because engineering work required all of that just to participate.
It is less reasonable now. Agents can handle a lot of the mechanical parts of engineering work, the parts that used to be the entry ticket. What is left is closer to describing what you want clearly, reviewing whether the result actually does that, and deciding what happens next. Those are not exclusively engineering skills.
I think the tools have not caught up to that yet. They are still built for people who already speak the tool's language fluently, which keeps non-engineers out of work they could otherwise meaningfully do. The interesting design problem is not making the tools smarter. It is making them legible to someone who has a clear idea and no git experience at all.