I think the backend bits were basically done with T310140: Create action API endpoint in Phonos. The only thing left now is to add the configuration setting to change which engine the extension uses. Thus, perhaps it makes sense to merge this into T311234: Create Larynx phonos engine? The reason being, we'll need a way to change the code to use the Larynx engine, so we might as well do that via configuration setting.

Also note T311233: Create Google phonos engine was moved to a future sprint since we need to hear back from legal before we know that our approach is compatible with Google's terms of use. So whenever we do get to adding Google (or any external API requiring a key), we'll want to add configuration settings for the API keys as described in this task, but I think that can also be done in tandem with T311233.

In T309707#8030839, @MusikAnimal wrote:

I think the backend bits were basically done with T310140: Create action API endpoint in Phonos. The only thing left now is to add the configuration setting to change which engine the extension uses. Thus, perhaps it makes sense to merge this into T311234: Create Larynx phonos engine? The reason being, we'll need a way to change the code to use the Larynx engine, so we might as well do that via configuration setting.

Also note T311233: Create Google phonos engine was moved to a future sprint since we need to hear back from legal before we know that our approach is compatible with Google's terms of use. So whenever we do get to adding Google (or any external API requiring a key), we'll want to add configuration settings for the API keys as described in this task, but I think that can also be done in tandem with T311233.

Agreed, thanks @MusikAnimal 🙂 I'll merge this into T311234: Create Larynx phonos engine