tl;dr If this is implemented with tags, consider a tag that encapsules the three content types. Just like "no-ai" encapsules the three content types plus code.
---
It will depend on the implementation/user interface to apply the ai filters for browsing.
If people want to browse for "non-ai games" and devs honestly disclose the usage of their helper's outputs, many games might fall under the "ai" branch because of code, but the player browsing for games might not care for mere code, only for art as in pictures and story.
This is a language and definition thing. But in a game, the code is not the content. It is the means to display the content.
There currently are those 4 sub filters to positivly select ai content.
1 AI Generated Graphics 2 AI Generated Sound AI 3 Generated Text & Dialog 4 AI Generated Code
"no-ai" is !(1||2 ||3||4)
"no-ai-artworks" would be !(1||2)
"no-ai-content" would be !(1||2||3) - on the basis that code is not content.
My point is, people browsing for assets would use "no-ai" to select apropriate assests for their no-ai project. Or select the positive sub tags for their AI-containing project.
But people browsing for games might prefer "no-ai-content". If there is only the full "no-ai" filter they would filter out lots of games that feature only human made art, but might fall under ai because of code.
I mean, people already use full engines to deliver their content. Coding is just not the same as content and art. I do not see much discussion about people wanting to filter out all the games that use a game engine, or code made with help of generative ai. But I do see people wanting to not play games that have AI pictures and AI story writing.