True when the tree came back truncated at the depth cap.
Worth surfacing rather than inferring: a truncated tree looks like a complete one, so a viewer
would believe a run ended where the query stopped reading. Callers should log this loudly AND
record it durably — a depth this large means either a genuinely pathological workflow or corrupt
ancestry, and both are things someone needs to see after the fact rather than in a log nobody
tailed.
True when the tree came back truncated at the depth cap.
Worth surfacing rather than inferring: a truncated tree looks like a complete one, so a viewer would believe a run ended where the query stopped reading. Callers should log this loudly AND record it durably — a depth this large means either a genuinely pathological workflow or corrupt ancestry, and both are things someone needs to see after the fact rather than in a log nobody tailed.