Designer here so take this with salt, but the schema work usually lands on our plate when contracts drift from what the UI promises. Curious if "data contracts" here means anything enforceable at the component layer or just better docs for the backend team.

Curious if the migration graph handles branch reconciliation cleanly. Our discovery system has a similar concept for tracking document versions across matters, and the edge cases around merging divergent histories ate months of engineering time.

Solo dev here, the migration graph stuff sounds useful but I'd want to know how it handles squashing in early stage projects where I rewrite the schema five times a week. The agent DX framing makes me nervous though, every time a tool optimizes for agents first the human ergonomics seem to regress a quarter later.