A route calls a subject nothing serves

Seen while sweeping the hand-written list requests. /api/counterparties/children answers 503, and the BFF log names the cause:

Request to ores.dev.jolly_knuth.refdata.v1.counterparty_business_centres.list failed: 503: 503

The shell confirms nothing serves that subject:

✗ Request failed: NATS request failed: no service is handling subject
  'ores.dev.jolly_knuth.refdata.v1.counterparty_business_centres.list'

The two lists beside it answer: counterparty_identifiers.list returns rows and counterparty_contact_informations.list returns an empty page.

So the entity exists in the model and the BFF reads it, but the refdata service registers no list handler for it, or registers it under another subject. Either the handler is missing from the service's registration or the BFF names the wrong subject; the model and the generated subjects settle which.

It is not the wire shape: the payload does not reach the service, so no decoder touches it. This capture is separate from the sweep for that reason.