Embedded WebExtensions can be shipped only as a part of Bootstrapped Extensions.
There is no resource to re-develop TST as a bootstrapped extension.
So now I'm planning to develop a version 0.99 just designed for migration. It will:
A bootstrapped extension with embedded WebExtensions.
The "outside" simply sends configuration and structure of existing tabs to the "embedded" via the messaging API.
"Embedded" will store the information to the local storage.
After that the version 0.99 will be updated to renewed WebExtensions version 2.x via auto-update.
Then the updated version will read migration data from the local storage and complete migration based on the information.
Now manual migration feature is landed. In legacy version you can export configurations and tree to files. On the other hand, you can import them manually on the WE version.
We need a migration path.
So now I'm planning to develop a version 0.99 just designed for migration. It will:
After that the version 0.99 will be updated to renewed WebExtensions version 2.x via auto-update. Then the updated version will read migration data from the local storage and complete migration based on the information.