I think "the pseudocode is persisted alongside the generated code" just reinvented jira/linear tickets and PR descriptions. We have ways of using git and tracing the code write to the thought process behind it.
The difference is that linear tickets, PR descriptions, git commits etc all track changes to the code, but not the code itself. You could read a changelog to understand the evolution of an application, but it wouldn't give you a stable, clear sense of what the intended product is right now.
Plus, it'll go stale as quickly as comments do. Some might be correct, but I think a lot of code gets fixed or changed pretty quickly, meaning the pseudocode is basically useless afterwards, unless it's updated... And that's a whole new effort.
