Hashing content plus tenant metadata into the doc ID handles retries well. A revised policy PDF hashes to a new ID, though, so as far as I can tell the old version's chunks stay indexed next to the new ones. I didn't see a superseded state in the lifecycle. Is retiring old versions part of the ingestion episode?