v0.25.1

The Java client no longer loses externalized batches.

0.25.0's headline was that a Java client can call a VGI worker. It could — but a worker that externalized an oversized batch (replacing it with a zero-row vgi_rpc.location pointer) had those rows silently discarded on the client: the streaming read path never resolved pointers, so a large scan returned a short result that looked complete.

Fixed in vgirpc 0.21.5, which this release pins. An unresolvable pointer now fails loudly instead of yielding an empty batch.

No change to this library's own code — worker-side behaviour is identical to 0.25.0.