-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Tiered Storage
-
None
-
Storage Engines - Persistence
-
172.339
-
SE Persistence backlog
-
None
Problem
A second pass after the leftover-remnant ticket found dangling tiered-storage references that are not post-removal notes: a live @skip_for_hook("tiered") after the hook is gone, comments that still claim flush_tier runs, a Doxygen snippet pointing at deleted ex_storage_source.c, AGENTS.md still listing src/tiered, stale comments in tests/block/schema, and tooling (callgraph, RTS verifier URI prefix) that still treats the removed tree as live.
Change
Strip those dangling references. Do not touch parse stubs (tiered_storage= / tiered_object), upgrading.dox removal notes, address-cookie objectid / WT_TIERED_OBJECTID_NONE, import, WT_BTREE_PREFIX, or the err.c URI allow-list. Those are remaining behavior or intentional notes. Validate each hit: drop live or wrong claims; keep a historical parser only if it still has to read old logs.
Test
s_fast. Python tests touched by skip or comment changes (test_eviction08 at minimum). No new behavior tests unless a leftover skip was hiding a live path.