I found another problem. The string
NOT "foo"[MESH] AND "bar"[MESH]
will result in the nonsense
AND "bar"[MESH]
I don't know if this (a unary NOT) is something you'll encounter

I found this problem while writting the RecParser version I just added as an update to 410587