Documentation

Handle the ServerReflectionInfo bidirectional stream for grpc.reflection.v1: answer every request on the incoming stream in turn, then forward the client's own terminal marker. A bidi handler that returns without sending NoNextElem itself has its stream cancelled instead of closed with trailers, the same requirement as for server-streaming handlers (both go through grapesy's identical sendOutput call . fromNextElem call path).

Handle the same stream for the legacy grpc.reflection.v1alpha, by bridging each message to and from v1 and answering with the one core answerReflectionRequest.

Answer one ServerReflectionRequest, dispatching on its message_request oneof.

Lookup failures (FileByFilename, FileContainingSymbol) are reported in-stream as an ErrorResponse with NOT_FOUND, never as a gRPC error: the RPC itself stays OK for the life of the stream. No proto file served here declares proto2 extensions, so file_containing_extension always answers NOT_FOUND, while all_extension_numbers_of_type answers an empty ExtensionNumberResponse for a type the server knows and NOT_FOUND for one it does not.

The fully qualified name of a proto service, <package>.<Service>, read off its own compiled-in descriptor via proto-lens's Service class. Deriving it this way, rather than writing out the string, means the name paired with each service's handler in Cardano.Rpc.Server and the name answerReflectionRequest (above) advertises for list_services can never drift apart.