The best I could figure is that I like to start with requirements, use AI to discuss and settle on its high level design and specific aspects of its implementation. I may or may not read all the code, but the key thing is even if I didn't read the code in advance, doing so would not be a surprise and I'd know what it was doing and how it was doing it because those were things I decided during the up-front conversations and not left as an open exercise for the AI. And coming back to the codeberg.org vote I can guess that it was elements like these that they wanted to guard. They don't want repos whose owners don't know what the code does in a technical sense or how it's constructed etc. There's likely other things too like seeing text that doesn't read like people wrote it and I find that tiring to read (in a literal way, I get drained from reading too much of it) and endorse minimizing that.
Another thought was that my ever long search for better and better programming languages was that if I have a clear vision of what I want the language should have the least friction to write it down. Some languages that feel closer than others were Elm, Elixir, F#/OCaml, Pony, Rust, Kotlin, Go. Only a couple of these are my languages I'd regularly used but would prefer to have my AIs write in them. For web I'd probably also accept Vue, Svelte, or (simple) React. In particular using Go for mini back-ends is particularly effective as the coding style tends to be regular and boring which minimizes differences between human and machine written styles. So in a sense giving specs at multiple levels of abstraction and detail is the perfect high level language I'd been wanting.