Answer
When pruning, ArgoCD reverses wave order—higher waves are deleted before lower ones—so dependents are removed before their dependencies (mirroring creation order). This prevents deleting a prerequisite while something still depends on it.
Real-world example On teardown, the frontend (wave 2) is pruned before the database (wave 1), the reverse of deployment order.