Currently, applications can directly access various WT internal structures through the public API, such as the history store (file:WiredTigerHS.wt), the metadata table (file:WiredTiger.wt) and the layered table constituent tables (.wt_ingest and .wt_stable).

Historically this behaviour has been a allowed on a case-by-case basis for two main reasons:

• to support correctness checks in testing
• to allow investigation and possible repair of corruption in the field

Consider introducing an optional admin mode configuration option to wiredtiger_open that enables access to internals. By default, it should be disabled to prevent accidental misuse while still supporting testing and debugging when explicitly required. 

Definition of done:

• Add an optional configuration option.
• Refactor existing python tests that access internals in this manner
• Appropriately document this change in the architecture guide.