There appears a single double quote in front of the string value. This behavior could break parsing of the output.
$ gpgconf --list-options gpg-agent | grep \" debug-level:26:1:set the debugging level to LEVEL:1:1:LEVEL:"none:: log-file:8:1:write server mode logs to FILE:32:1:FILE:::"/tmp/gpg-agent.log
No, that is the convention used by gpgconf. See https://gnupg.org/documentation/manuals/gnupg/Format-conventions.html#Format-conventions:
string
If the option takes a string argument (alt-type is 1), and it can only occur once (list flag is not set) then the option argument is either empty (only allowed if the argument is optional), or it starts with a double quote character (") followed by a percent-escaped string that is the argument value. Note that there is only a leading double quote character, no trailing one. The double quote character is only needed to be able to differentiate between no value and the empty string as value.Oh, my bad. Someone on IRC said it was a bug and I didn't look at any further details.