The transport is not a thin fetch helper. It is the place where mutation names become concrete backend requests.
It must acknowledge or reject every mutation, return canonical deltas, and preserve client-generated IDs when the backend accepts them.
If the app already fetched remote data, the transport may stay out of the way and VibeLayer can reconcile those deltas directly.
That boundary keeps backend coupling away from component logic and makes retry behavior understandable.