`parse_service_endpoint_changes` will happily accept the same protocol in both `enable` and `disable` (or multiple times), producing conflicting duplicate `ServiceEndpointChange` entries in the request. This makes the request ambiguous and can cause hard-to-debug API errors. Consider detecting conflicts/duplicates (e.g., by tracking seen protocols) and returning an error if a protocol is specified more than once or specified in both lists.

[sdairs]

parse_service_endpoint_changes will happily accept the same protocol in both enable and disable (or multiple times), producing conflicting duplicate ServiceEndpointChange entries in the request. This makes the request ambiguous and can cause hard-to-debug API errors. Consider detecting conflicts/duplicates (e.g., by tracking seen protocols) and returning an error if a protocol is specified more than once or specified in both lists.

Originally posted by @Copilot in #25 (comment)