v1.2.38

• A key-value store record write (Actor.setValue, KeyValueStore.setValue) is no longer lost to one failed answer. Each write now sends an Idempotency-Key, and when its answer is lost (a 502/504 page from the edge or load balancer, a dropped connection, a timeout) it is sent again with the same key; the API applies and counts it once. Before, the write was never re-sent, so one such page on the final OUTPUT write failed the whole run. An API that answers a keyed write without X-Scrapely-Idempotency (an older server) gets no re-sends, as before.