And that test winds up in v0.1.1 of your software magically, or is it there because you put it in the work to add it up front?

Nice work on the false dichotomy. :)

TDD has a very specific meaning. It means you write tests, then write code that passes those tests. That specific order. If you're not doing that, you're not actually adhering to the definition of TDD.

TLD could mean, for example, writing a module, class, or function with a defined interface that implements the contracts for that interface, then writing the suite of tests to validate that module, after which you move onto the next module.

Strangely enough, you can do that while you're developing the product without adhering to the process dictated by TDD.

You seem to be conflating the existence of unit tests with TDD.