v0.4.25 — Quieter Reads Through `api`

A read through robot-council api now starts an ephemeral session. This is the client half of keeping a loop of reads from filling the fleet feed with a join and an end for every call. The fleet stops announcing those sessions once robot-council/core#424 ships. Until then a read behaves as before, because a service that does not know the flag ignores it. A call that can change something still starts an ordinary session and ends it.

What's fixed

• Start an ephemeral session for a read through robot-council api #310