If I forget the @Spatial annotation, the query involving .spatial() should fail with an explicit exception.

Hmm, there seems to already an exceptional case - HSEARCH000131 - which gets thrown from ConnectedSpatialQueryBuilder. I changed the message a bit and added some additional tests. Not sure if there is another case you had in mind? HSEARCH-1708 is still of course another issue.