The capability coherence rule table: every flag an adapter claims must be
backed by the matching implemented surface. The two retrieval flags are
checked BOTH ways — they gate conformance assertions rather than only
describing the provider, so denying an implemented read would buy silence.
Returns one message per violation, in rule order, empty when coherent.
@payfanout/server's PaymentService rejects registration on the first
violation and the conformance suite asserts an empty result — both consume
this single implementation so the two can never drift.
The capability coherence rule table: every flag an adapter claims must be backed by the matching implemented surface. The two retrieval flags are checked BOTH ways — they gate conformance assertions rather than only describing the provider, so denying an implemented read would buy silence. Returns one message per violation, in rule order, empty when coherent.
@payfanout/server's PaymentService rejects registration on the first violation and the conformance suite asserts an empty result — both consume this single implementation so the two can never drift.