docs: collision cleanup no longer deletes — excluded rows age to inactive

[MrAlders0n]

Follows server 26df9c9, which removed Logic 1 (the prefix-overlap duplicate delete) from repeaters_cleanup.php and widened Logic 3 to enabled IN (1, 2).

What changed on the server

Collisions are now handled entirely by the collision system at ingest (repeater_collision.php + backfill_repeater_collisions.php / fold_corrupt_twins.php). Nothing is deleted on a 3× stale timer any more.

Instead, a colliding repeater that goes silent is marked Inactive at repeater_inactive_days (default 30). That drops it out of the collision recompute's live set — which only considers enabled IN (1,2) — so its partner is restored on its next advert instead of being pinned at Excluded forever.

Two user-visible changes: the timeline moves from 72 hours → 30 days, and the outcome from deleted → Inactive.

admins.md

• Dropped the 72-hour row from the lifecycle table, and the whole Duplicate collision cleanup subsection — including the survivor-restore behaviour, which no longer exists
• 3× stale is now attributed to pending resolution alone (it was "the two routines below")
• Repeater Inactive After now covers Excluded rows, and explains why that's what unsticks a stale collision
• Excluded status and Bypass Auto Delete corrected — the latter no longer skips a stale-duplicate delete, but does now hold a colliding partner excluded while it's away, which is worth an admin knowing

duplicaterepeaterid.md

Automatic Cleanup rewritten. It previously described deletion at 72 hours as the primary resolution path, which is now wrong end to end. Neither repeater is deleted; the survivor returns on its next advert; a returning repeater is re-excluded if the ID is still ambiguous.

🤖 Generated with Claude Code

https://claude.ai/code/session_01KojjSrgSQQJW7Z8b3eakEA