Repository navigation
docs(roadmap): re-head the AdGuard probe entry to #102, not closed #123 - #301
Merged
Merged
Conversation
The entry was headed #123, which closed on 2026-09-04. Its body already said the remaining work "belongs to #102" -- uncommenting the target once the machine exists -- so the heading was the only part still pointing at a closed issue. Re-headed rather than deleted, because the work outlived the issue. #123 asked whether moving DNS off the gateway adds a quiet way for the house to lose the internet; ADR-0010 and the verification appended to it answered that. #126 was the same detection filed separately and closed with it. What survived both is one paragraph of #102's build. Also records why the family-runbook line is held rather than pending, and names the two Lemmiwinks edits that come due in the same sitting: the "there isn't a Pi-hole" bullet stops being true once a filter exists, and dns_is_broken's source note deserves a line saying this was the one thing that did need writing. The half that was actionable already merged as Gerrrt/Lemmiwinks#169. No claim about the detection changes. #291 built it, measured all four states against a real AdGuard first, and this entry keeps saying so. Refs #102 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
The AdGuard probe entry under Monitoring was headed #123, which closed on 2026-09-04. Its own body already said the remaining work "belongs to #102" — uncommenting the target once the machine exists — so the heading was the only part still pointing at a closed issue.
That is the failure this file keeps catching in itself; #285 moved #97 to Done for the same reason a day earlier.
Re-headed, not deleted
The work outlived the issue:
targets/blackbox-dns.yaml, two lines and a verify.So it is filed under #102 rather than left as a dangling pointer.
Also recorded
Why the family-runbook line is held rather than pending: there is no filtering to lose yet, so it would describe a symptom that cannot occur. And the two
Gerrrt/Lemmiwinksedits that come due in the same sitting — the "there isn't a Pi-hole" bullet inrunbooks/dns_is_brokenstops being true once a filter exists, and that page's source note deserves a line saying this was the one thing that did need writing. The half that was actionable already merged as Gerrrt/Lemmiwinks#169.No claim about the detection changes. #291 built it and measured all four states against a real AdGuard Home first; this entry keeps saying so, including that it was right about the probe needing to bypass
morpheusand wrong only about the target versus the rules.Docs only.
make lintandmake check-docspass.Refs #102
🤖 Generated with Claude Code