v5.7.0

Nuthatch 5.7.0 keeps an address-history nest answering when one part of its backfill cannot, and says
in /ready how far each kind of data is served. There is no storage migration.

Both faults came from running rotki's validator support against a live mainnet nest, where a single
trace_filter window timed out on every poll.

One failing window no longer stalls the nest

A backfill window that failed marked the whole cursor stalled and was tried again every poll at the
same cost, and block bodies and produced-block proofs waited behind every trace window (#2078). An
address whose window fails now backs off on its own: the window halves down to the floor, then waits
1, 2, 4 and up to 32 polls between tries, while the other addresses, block bodies and produced blocks
carry on (#2080). Address discovery takes at most one poll interval a pass before the others take their
turn. /ready still reports stalled, now only while a pass advances nothing, and lists each address
whose windows keep failing under stalled_backfill, with its failures, span, retry_in_polls and the
last error.

Withdrawals and mined blocks need only bodies

A withdrawals or mined-blocks request waited on trace discovery although both come from block bodies
alone (#2076). With discovery stuck far behind, a range ending at the head was refused as covered
through the discovery front, nine million blocks short of where the bodies were. They are now judged
on body coverage, the refusal names how far the bodies are, and a short tail above them is read on
demand (#2079). /ready gains served_through: per family the nest serves, transactions, bodies
on Ethereum and produced with mev_relays, the block every watched account is covered through, so a
client can stop there (#2077). It adds fields and changes none.

Gated on Lodestar's data

Every change is in the address-history path, which none of the gated nests declares, so this release
changes no query path the release gate measures. The gate now runs against copies frozen on 2026-10-12,
with the previous release as its baseline (#2075).

Compatibility and upgrade

Replace the binary and restart. A 5.6.3 store is used as it is.