For single-library repos, the whole repo is the source root. After testing, it seems this can't be represented with our current state schema. gax-go is one example of this, with source code really in the root directory.

Note that we might be able to handle the google-cloud-go "main" module differently to the use case for this issue, as that only has source code in subdirectories. I suspect most other single-library repos have the actual source code under directories, and could handle listing the specific files to manage in the root as global files.

So we have options of:

• Design support in the Librarian CLI for "single library repos" - requires some design work as well as implementation, but then each single-library-repo would be easily represented
• Configure each single-library-repo in a slightly odd way

The first option would be cleanest, but takes some up-front work.