Query needs to allow continuing a transaction that does not have mutations

If I do this:

transactions.run((ctx) -> {

   ctx.get(collection, "doc1");

   ctx.get(collection, "doc2");

   ctx.query("SELECT ...");

}); 

This results in an error coming back from the BEGIN WORK of:

{"code":17006,"message":"Start Transaction statement error: No bucket named "} 

My understanding from Sitaram is that this is caused by doing a BEGIN WORK with zero mutations.

But this is perfectly valid.  There have been some read operations done inside the transaction before the query, and there is a transactionId, attemptId, and a transaction configuration.  So we are not starting a fresh transaction at the ctx.query point, but instead continuing an existing one, and this should be permitted.