Regrettably this seems to be a bug with a particular version of GraphQL in the environments. The team at AEM Cloud Services rolled back to an older version of the environment and the GraphQL query began working again. I would love to know what the underlying cause is, though.