wiki: 0.4.0 (in-memory probe, ordered chain, plain fallback)
Update wiki to 0.3.0: state machine, hysteresis thresholds, configurable interval, strict enforcement, device-mode diagnostics
docs: wiki for 0.2.0 — verified facts, real endpoint names, sidebar
Pages were rewritten for 0.2.0 in 2e31ad0 but kept fourteen statements the code
does not support. Each fix below was checked against the repository, not against
memory:
- Home: drops "field-checked on 7.25" — only 7.23.1 and 7.24.5 are recorded, and
the page now says the repository wins when the two disagree.
- Configuration: the bootstrap block gains the missing dns.google 8.8.4.4 record
(01-configure-doh.rsc pins four, two per host), and `filtering` is described as
what it is — a marker the monitor never reads.
- Monitoring: algorithm semantics corrected (the script creates services with
algorithm=1, "at least one child", which is what the 2026-10-26 measurement
showed; the page had 1 and 2 swapped), the collector snippet gains the MON and
CLK lines without which doh.monitor cannot be built, doh.monitor is described
as the scheduler entry the collector actually looks for, service trees carry
their real Cyrillic names, and the Zabbix API credential comes from the
environment.
- Health-Monitor: the restore command returns to cloudflare-dns.com, the 0.2.0
default, instead of the Family endpoint.
- Upgrading: a 0.1.0 Family install leaves dead bootstrap records behind — said
so, plus what re-import is actually needed.
- Verification: fleet table no longer invents a RouterOS version or a per-model
device-mode that contradicts the README matrix.
- Flow: seven diagrams, not six.
- New _Sidebar.md (navigation) and _Footer.md (source-of-truth rule).
docs: wiki for 0.2.0 — stub pair, content-aware health check, DoH-to-DoH failover