For other issues:

• I do believe Theo's frustration with GraphQL field asserts can be mitigated using qgl.tada as asserting every schema field (e.g. [Foo!]!), as it uses a tsconfig plugin and LSP for type safety. However, the code savings are negligible (I implemented it but decided not to include it in the above PR). In Theo's gql.tada video itself it also included syntax highlighting for "unused" field, but couldn't replicate it. This method might have saved him frustration with his current codegen approach.
• Code Gen in go is possible, but to have DB annotations it'd require extra config (if using https://github.com/99designs/gqlgen per LLMs suggestions) that's equivalent to the hard-coded typings. With graphql-codegen-go they auto populate code similar to the current go-structs, but they auto gen many all possible types that aren't used which will increase the "LOC" metric.