it’s the QUERY_STRING decoded if it’s a search-string (i.e. not a key-value pair.) It’s useful for scripts to avoid percent-decoding the querystring in the most common case of a query, because in Gemini querystrings key-value paired are not common. Idea from a discussion with Allen Sobot.

RFC3875 § 4.1.7 states that "the QUERY_STRING variable contains a URL-encoded search or parameter string".

and remove the explicit mapping from the documentation and test files.

if using `types' the internal listing is not used, so show how to add the entries for text/gemini when using /usr/share/misc/mime.types.