I think I'm in the minority of cases here but I can't find any discussion anywhere on the topic:
When I started the application process for git access the single project promotion didn't exist. During the time it took to get the project approved, the single project promotion was created and given to my project upon approval. The project at the time had more than the required amount of code just not the correct "number of functions". If I had known this I would have refactored it into a couple of extra helper functions, but I didn't have a chance to change it prior to approval. I replied back to the issue asking if this was possible and got no reply https://www.drupal.org/node/2098719 . Time has passed and the module has grown substantially, sub-modules, more integrations and we've got sites using it now. EDIT: Wanted to add that I did create a new task in the queue for review at: https://www.drupal.org/node/2676732 but don't know if that's the right way and I don't think anyone really knows what to do with it from a review process as it's sat there for a few weeks now.
As I said, I'm likely in the minority of folks that have single project status to have this situation but is there a way to re-apply for full status? I feel as if there should be a fast-track or a process given that person has already been through it once they should be able to show they meet the coding standards, meet the code length requirements and be given the full status.
I understand the process is undergoing changes and is a tremendous effort on the part of those that run it. More clarity around the single project status and how to avoid it if you don't want it would be great. I think I got caught in a funky time where it didn't exist, then it did, but no one really knew what to do with it.
I saw the text suggested last year on a post and think that's great, no where on the pages does it talk about this status that I could find and could be very discouraging for upcoming developers who are new to Drupal.