Major - P3 This is a spin-off of WT-17272, which described three correctness gaps in the follower's in-memory truncate-list write-conflict detection. That ticket was closed with items (2) and (3) resolved. Item (1) was explicitly dropped from the PR scope and is still TODO.
Gap (1) — search_near ingest truncate misses uncommitted ingest updates
The follower truncate path positions via search_near before calling _wt_range_truncate. Because search_near is a read operation, it does not trigger _wt_txn_update_check. As a result, write conflicts against uncommitted ingest updates that fall within the truncate range are silently missed — conflicting operations can commit when one should roll back.
Proposed fix location: __wt_insert_truncate_entry — the conflict check needs to be invoked there so that truncate-range positioning via search_near is covered.