No rush if it's not ready for even that much public mention. It just struck me that questions like this could be preliminarily answered on the website, rather than leaving the impression that C/C++ support is not under consideration.

As mentioned in the other thread(s) - I'm currently working on adding basic Catch (and/or Gtest) support before the PR is ready for review. So, it will basically be first-party code support that's been tested on a bunch of my repos with a lot of sub-libs. Lots of work before it's anything I'd even want to promote to `experimental`/`muslin` /`othermagicword`

"Exploratory" sounds apt wrt the C/C++ support, if you're comfortable having something be said. If not, we can put that on hold.

Alternatively, for upcoming support, we could go the approach of detailing major milestones and referencing those in the docs

Aside: I think Kotlin/Jetbrains really nails stability levels, both in description and the end result https://kotlinlang.org/docs/components-stability.html