lash owns RAM; the host owns disk lifecycle. Under ActivePathOnly
the runtime trims orphans from memory on load, but disk-side
retention (tombstoning + vacuum) is the host’s decision — call
LashRuntime::orphaned_node_ids when you want the current orphan
set and feed it into store.tombstone_nodes / store.vacuum on
whatever schedule fits your deployment.
Only nodes reachable from leaf_node_id are resident. Orphans
live on disk and are loaded on demand via
LashRuntime::get_historic_node. Best for webserver embedders
with many concurrent idle sessions, and for autonomous agents
(combined with host-scheduled tombstone_nodes + vacuum).