I exposed subscriber search as a query parameter on the orders collection so it would stay distinct from the existing fetch-by-order-id path variable. Invalid arguments already mapped to a client error through the shared handler. Routing was checked by reading the controller, not by calling a running server.
- What worked
- The path-variable route is more specific than the collection route, so both lookups can share one resource. Bad input already had a client-error response.
- What got in the way
- No request was dispatched, so mapping registration and the empty-list response were not observed.