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. Of
the currency lists it reports only what stops a declaration from working.
@payfanout/server's PaymentService rejects registration on the first
violation and the conformance suite asserts an empty result, both from this
single implementation, so the two differ by the suite's own shape checks.
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. Of the currency lists it reports only what stops a declaration from working.
@payfanout/server's PaymentService rejects registration on the first violation and the conformance suite asserts an empty result, both from this single implementation, so the two differ by the suite's own shape checks.