Shadow evaluation

A replayed eval job carrying a production write key committed its late result to the shared store

Sharing one idempotency key let a late shadow eval result commit to production, according to a dev.to design review written for MonkeyCode. Its fix rewrites the key at admission and separates the queues too, at the cost of diffs that are harder to read.