Type based bind in multi library environment

Hi,
Im trying to understand how to scale my type based bind usage in multi lib build.
I have the same ip compiled 3 times and I have 3 instances, each from different library determind using instance configuration rule.
I have global scope type based bind that add checker to each IP.
I would like to be able to configure the bind somehow so checker from lib1 will go to IP from lib1 and same for IP2…
For Ip3, there is no checker compiled to ip3 library so I expect no binding…
Any way to achieve that?
I saw there is a mantis talking about bind and libraries, this should have been fixed in 2023 LRM, but I couldn’t understand from the LRM or the mantis what is the way to use the new LRM change.

//bot.sv
Module bot;
endmodule

//mid.sv
module mid;
endmodule

// top.sv
module top();
mid m1();
mid m2();
mid m3();
endmodule

config cfg;
design worklib.top;
//default liblist worklib;
instance top.m1 use lib1.mid;
instance top.m2 use lib2.mid;
instance top.m3 use lib3.mid;
endconfig

module binds_mod();
bind mid bot b();
endmodule

xrun -compile -work lib1 bot.sv mid.sv
xrun -compile -work lib2 bot.sv mid.sv
xrun -compile -work lib3 mid.sv

xrun -elaborate top.sv cfg.sv -top cfg -top binds_mod

I believe you are referring to 07242: Binds are non-scalable in the presence of config libraries - Accellera Mantis

I don’t think that issue covers the case you are looking for.