Message routed to two queues when it matches multiple Publish rules (base class + interface)

[ali-pouneh]

Summary

When a message type inherits from a base class AND implements an interface, and there are
separate Publish rules for each, Wolverine sends the message to both queues. I need
mutually exclusive routing: deduplicated messages should go ONLY to their deduplication queue,
and non-deduplicated messages should go to the default queue.

Setup

I have a hierarchy of events all deriving from AppEvent, and a set of marker interfaces
for Azure Service Bus duplicate detection with different time windows:

public abstract class AppEvent
{
    public required int TenantId { get; set; }
}

public interface IDeduplicatable
{
    string DeduplicationKey { get; }
}
public interface IShortDeduplicationWindow : IDeduplicatable { }
public interface IMediumDeduplicationWindow : IDeduplicatable { }
public interface ILongDeduplicationWindow : IDeduplicatable { }

A concrete event implements both:

public class OrderUpdatedEvent : AppEvent, IMediumDeduplicationWindow
{
    public int OrderId { get; set; }
    public required string Status { get; set; }
    // ...
    public string DeduplicationKey
        => $"OrderUpdated_{TenantId}_{OrderId}";
}

My routing configuration registers a publish rule per deduplication window, plus a catch-all
for AppEvent:

private static void ConfigurePublishing(WolverineOptions opts)
{
    // Deduplication queues (one per window length)
    opts.Publish(r =>
    {
        r.MessagesImplementing<IShortDeduplicationWindow>();
        r.ToAzureServiceBusQueue("app-queue-dedup-short");
    });
    opts.Publish(r =>
    {
        r.MessagesImplementing<IMediumDeduplicationWindow>();
        r.ToAzureServiceBusQueue("app-queue-dedup-medium");
    });
    opts.Publish(r =>
    {
        r.MessagesImplementing<ILongDeduplicationWindow>();
        r.ToAzureServiceBusQueue("app-queue-dedup-long");
    });

    // Default queue for all other events
    opts.Publish(r =>
    {
        r.MessagesImplementing<AppEvent>();
        r.ToAzureServiceBusQueue("app-queue");
    });
}

Each deduplication queue has RequiresDuplicateDetection = true on the ASB side with
an appropriate DuplicateDetectionHistoryTimeWindow.

Problem

When I publish an OrderUpdatedEvent, Wolverine matches two rules:

1. IMediumDeduplicationWindow → routes to app-queue-dedup-medium
2. AppEvent → routes to app-queue

So the message is delivered to both queues. The consumer processes it twice.

Desired behavior

• If a message implements any IDeduplicatable interface → send only to
  the matching deduplication queue
• If a message only extends AppEvent (no deduplication interface) → send to the
  default app-queue

What I've tried / considered

• Ordering the publish rules (deduplication rules first, AppEvent last) — doesn't
  help, Wolverine evaluates all matching rules.
• Using a custom IMessageRoutingConvention — seems like the right approach but I'm
  not sure how to properly implement exclusive routing with it.

Question

Is there a built-in way to make publish rules exclusive / first-match-wins? Or is the
recommended approach to use a custom IMessageRoutingConvention that inspects the message
type and returns only one endpoint? If so, could someone point me to an example?

Any guidance appreciated. Thanks!