Even though the experimental plugins docs have been removed, is the plugin_settings model config concept relatively "safe"?

[blakeNaccarato]

I ask because I'm using e.g. MyModel.model_config["plugin_settings"]["my_plugin_config_that_i_can_rely_on"] to facilitate a certain extension to Pydantic.

I AM NOT using the entrypoints or custom logic hooks that were in the docs, removed since #10176. I don't intend to use that element, I just need a "relatively safe" config space in the Pydantic model config to facilitate my tool.

I know this is all experimental feature territory so any answer will be tentative at best. Am I being reasonable in assuming, at the very least, that model_config will continue to have a mapping (not necessarily called plugin_settings) in which plugin developers will be able to have a key with a config object of their own for an eventual plugins feature?

Also a quick note on the plugin feature space, I would love it if the Pydantic plugins of the future had the power to customize the info.context element available during validation and serialization!

Thanks!