docs(admin): document the repeater lifecycle & data cleanup settings - #7
Merged
Conversation
Groups every ageing/cleanup control into one "Repeater Lifecycle & Data Cleanup" section mirroring the panel's "Repeaters & Data Integrity" block, with a lifecycle-at-a-glance table and worked examples per setting: - Stale Repeater Age (and its two 3x rules) - Repeater Inactive After (newly configurable, was hardcoded 30d) - Repeater Retention / Auto-Delete — the clock runs from last advert heard, not from when the repeater went inactive, so the windows overlap; a sub-minimum value is rejected outright rather than clamped - Ghost Retention, and why ghosts are the evidence base for pending links - Pending Link Distance, incl. why the default is 200 km - Stale Ping Cleanup — the grace clock (picking a window does NOT delete the existing backlog), plus the Backfill Purge preview/confirm flow Also documents which settings a multi-region group controls vs. which stay per-region, the Pending Repeater Links alert (evidence tiers, the three choices, self-clearing suppression, the two refusal cases), the Suspicious Live Sessions alert, and the three new notification events. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KojjSrgSQQJW7Z8b3eakEA
This was referenced Aug 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents the new regional admin panel (
dev/admin.php) cleanup features, grouped the way the panel groups them.What's new
A single Repeater Lifecycle & Data Cleanup section under System Settings, mirroring the panel's Repeaters & Data Integrity accordion. It opens with a lifecycle-at-a-glance table (what happens at 24h / 72h / 30d / never, and which setting drives each stage), then covers every control with a worked example:
Two behaviours worth calling out
Both are documented as the code actually behaves, which differs from how the in-app help text reads:
The panel's warning box will be updated separately in the server repo to match.
Also covered
🤖 Generated with Claude Code
https://claude.ai/code/session_01KojjSrgSQQJW7Z8b3eakEA