[...]
> continue to be runtime-linked with the library version it was compiled
> with.
Since I (IMHO justifiedly) complained about this, I shouldn't be using
this particular statement myself: Compiling and linking an application
doesn't result in any "implicit relation" to any particular dynamic
library (file) beyond recording a soname determined in the way I
described in the resulting binary.
The compiled application will depend on a specific set of interface
definitions (however acquired), but that's a whole different can of
worms I don't plan to dive into right now.