What's Iron's policy about soon deprecated MV2 extensions?

[freddie73]

I am a happy user of Iron browser for several years.
I'm very glad that Iron allows extensions to be installed and updated via .crx files as well (something that Chrome no longer allows except for the Linux version).
I think it's the perfect way to effectively simulate updating an extension before it's released in the store.
Specifically, it is very useful for checking whether the extension will be disabled whenever a wider permissions request is encountered in the new version.

Since I consider your policy undoubtedly "more open" than Chrome's,
I'm here to ask you how Iron will behave when it will be no longer possible to install MV2 extensions from the CWS.
It would be great if Iron allows these extensions to be installed at least locally.
Even more fantastic would be if the MV2 extensions, previously installed after the latest deadline, are not purged by the browser as Chrome appears to do.
Have you already made any decisions about it or are you considering these aspects?

Thank you in advance

[freddie73]

Not all together, please!