We already use a shared subscription with

KeyShare

option, since we do want messages to be processed in order per Key (this is something our design requires)

“Is there any Pulsar pattern, config, or upcoming feature that supports dynamic per-message key assignment instead of sticky key-range ownership?” No, you would have to implement something inside your application code to handle this scenario.