Source: PR #60 review (Important, non-blocking; confirmed no-op).
Records already marked as duplicates by a prior --execute run are never upgraded to deleted by a later --execute --delete run — escalation is silently a no-op. That may be the safe intended behavior, but it is currently undecided and undocumented.
Decision needed: either (a) document mark-then-delete as deliberately non-escalating, or (b) implement escalation gated behind an explicit flag. Note: interacts with #63 (cross-run visible-survivor gap) — resolve together.
Source: PR #60 review (Important, non-blocking; confirmed no-op).
Records already marked as duplicates by a prior
--executerun are never upgraded to deleted by a later--execute --deleterun — escalation is silently a no-op. That may be the safe intended behavior, but it is currently undecided and undocumented.Decision needed: either (a) document mark-then-delete as deliberately non-escalating, or (b) implement escalation gated behind an explicit flag. Note: interacts with #63 (cross-run visible-survivor gap) — resolve together.