I wrote https://github.com/mmastrac/clitest because I needed a more complex testing harness for CLI tests that does something similar. It's not exactly the same, but it's definitely in the same universe.
One-file-per testcase like `tc` does works, but it tends to fall apart a bit at large scale in my experience.
Integration tests are language agnostic too: you drive a browser through your app and all it matters is the output.
In this tc framework all it matters is the output of the command. The only part that must be customized to adapt to different languages is
result=$(command)
It's at https://github.com/ahoward/tc/blob/main/specs/002-we-need-a/...
While I can’t really comment on how good this specific implementation is simple diff based testing frameworks like this dont get enough press. My first job involved working on an internal programming language. The test suite was just a ton of statements that were executed top down and their output was compared against a single file. Yes that’s a bit absurd but it worked remarkably well. If they’d bothered to add a bit more structure around it I think it would have been perfect.