Context

WT-17996 changed the layered-table drop path so __drop_issue_trim reads the btree ID from WiredTiger metadata without opening the stable constituent. This allows a drop to be retried after the page service has already discarded the table's data.

MongoDB needs end-to-end coverage through the real PALI and SLS stack. The existing WiredTiger test uses PALite and directly removes its rows, so it does not cover page-server reclamation, object-store reclamation, or the MongoDB drop-pending ident reaper.

Motivation

A physical ident drop can be retried after its pages are no longer available. Before WT-17996, __drop_issue_trim opened the stable constituent to obtain its btree ID. Opening the handle reads the root page, so the retry fails before paliTrim when that page has already been reclaimed locally and from object storage.

The MongoDB regression test should establish that the fixed drop path performs no page read and still issues the trim against an already discarded table.