Here's the thing I've discovered, that makes using Gherkin+AI so awesome:
You don't need to automate the Gherkin.
Just write the .feature files in high detail, and then skip the steps. And then just ask the AI to make sure to check against the Gherkin. And, if you want something changed, just adjust the Gherkin by hand and ask the AI to implement the changes to match the new description.
The models _are_ the test automation.
It's like you architect a software bluebrint and the AI is the builder.
And, after it builds things, you can go in and rearrange everything, to your liking, and then say, "I changed the code. Please double-check that I didn't break the features," and it'll go through and mark everything that conflicts.
And, if you get tired of your code, delete the entire /src/ and say, "Please generate all of the code to implement the .feature tests." and it'll write it all out, neatly, in 5 minutes.
This is the way.
Code is disposable.
Creativity and some discipline in getting thoughts down coherently is where the value is now.
Wild.
The code is disposable is actually turning into a software architect's dream, which I didn't see coming. As he can use a prototype to hone the behavior, and then generate lots of different implementations to fulfill the behavior, and then pick the one he likes best and architect it even harder.
