On a disaggregated follower, a layered cursor value that is byte-identical to the internal tombstone (the two bytes 0x14 0x14) is reported as WT_NOTFOUND on read instead of returning the stored value.

Repro: on the follower, insert a key with value b'\x14\x14' (which lands in the ingest table), then search for that key. search() returns WT_NOTFOUND. A longer value sharing the same prefix (e.g. b'\x14\x14\xff') round-trips correctly.