Chatted with jam@ offline and we agree that trying to get waterfall/CQ coverage for something like this is probably too much effort to be worthwhile.

To extend the original issue, we want to manually track *all* revisions (back to, say, the date of this bug report) where the protocol has changed, and ensure that any new local EDK protocol change is compatible with those previous revisions.

This unfortunately means local testing only, as infra supports one revision, one build, one binary; and the nature of these changes is such that conditional behavior or mock data is an intractable solution to the problem.

Shouldn't be too bad since only a small number of engineers are making EDK protocol changes, and such changes are still (and should remain) quite rare.

Marking obsolete in favor of mojo_core shipping