Following discussion with @eddyashton, attempt to modify the consistency spec, in a minimal way, to allow for constructive Invalid (i.e. allow both the StatusCommittedResponseAction and the StatusInvalidResponseAction to make decisions about the future commit history).
This should be a no-op from an MC perspective (to be confirmed by the full CI), but would facilitate trace validation by allowing Invalid to be matched even when the known commit history doesn't extend far enough.
Following discussion with @eddyashton, attempt to modify the consistency spec, in a minimal way, to allow for constructive Invalid (i.e. allow both the StatusCommittedResponseAction and the StatusInvalidResponseAction to make decisions about the future commit history).
This should be a no-op from an MC perspective (to be confirmed by the full CI), but would facilitate trace validation by allowing Invalid to be matched even when the known commit history doesn't extend far enough.
Quite tentative.