Currently, write conflict detection against uncommitted fast truncates on layered tables is performed at the cursor layer. The function wt_layered_table_truncate_detect_write_conflict (in src/txn/txn_truncate.c) is called explicitly from two places in the layered cursor write path (in clayered_put and clayered_remove_follower in src/cursor/cur_layered.c).

Every cursor write operation on a follower must explicitly consult the truncate list before proceeding. Investigate whether this conflict check can instead be performed below the cursor layer, so that the layered cursor no longer needs a direct dependency on the truncate list.

If feasible, refactor to push the call site down the stack accordingly.