Comment 2 for bug 1577967

It is reasonable to have the "first" stream in multibufferstream scenarios be the stream that is affected by these client API calls. We'd have to break client API to root this concept out, which I don't think we have to do right now... seems to me this bug would be resolved by adding some tests to check that mir_surface_is_valid() works properly.