I work on a small team maintaining multiple services and this is very similar to our approach. Although I generally find review easier _without_ splitting every

I work on a small team maintaining multiple services and this is very similar to our approach. Although I generally find review easier _without_ splitting every PR by backend/frontend. The additional context helps and you don't have to switch back and forth between two sets of files/changes to make sure the interfaces align. Good ol' feature branches are also useful when you have multiple interdependent breaking changes. P.S. Bruno if you see this please skip the LLM fluff-up next time. It makes it hard to read.