Feature authorship: One per git project kind of sound supported?

Hello, I have been getting happily getting into Features and I have a few I want to create.

Now I try my best not to bundle parts of code together if they don't need to be. Divide to conquer kind of thing. So that's the angle I took first, trying to create one git project per feature, and use git tags as feature versions.

I got it working.. but it feels like I'm fighting against the system or I am not doing it right.

* The documentation on containers.dev is worded in a way that seems like you can have 1 feature per git project but without any details of that.
* The devcontainer-cli seems to work and be aware when asked to package/publish a single feature or a collection of features.
* Features have versions, but it's not clear to me how those versions are expected to get bumped in a collection. Seems untied to any source code tags. (at the moment I just use 0.0.0 in the json file and use sed replace in pipeline before publishing)
* devcontainer cli features test, this one seems to really not want to work with anything else then a collection structured as src/pkgName and test/pkgName. Anyway to make that work in a single repo mode where src/ is the feature and test/ is that feature test?

Any clarity on the above would be appreciated, here or maybe in the docs. I cannot be the only one that would naturally try to split those features into different projects :P

Thanks!

Lies die Feature-Dokumentation von containers.dev sowie die hier referenzierten Packaging- und Testbefehle der devcontainer CLI. Bestimme, ob Single-Feature-Repositories, Versionsaktualisierungen und das Layout src/ plus test/ unterstützt werden; abgeschlossen ist die Aufgabe, wenn der unterstützte Workflow dokumentiert oder die erforderlichen Spec- und CLI-Änderungen definiert sind.

Vom Indexierungsmodell aus dem Issue-Text verfasst.