docs: record generic monitor fault acceptance

Co-authored-by: GPT-6 <gpt-6@openai.com>
This commit is contained in:
ZeusinaandGPT-6 Bot committed 2026-10-14 01:06:19 +03:00
1 parent 5c85f3f0b9
commit 2242643000
3 files changed
+29 -6

No files matched your search

+10 -3
View File
@@ -39,9 +39,16 @@ old SS1080/Xray were untouched. Historical LIVE observations below are not curre
production availability. No network operations or deployment accompany this update.
Check-only neither selects/applies strategies nor writes strategy DB entries or
declares full-service READY. Generic periodic controller/config/strategy DB,
plugins/autotuning, maximum strategy collection, safe PID1 BLOCKED stay-alive and
Prometheus metrics remain TODO. Three-CDN discovery/qualification is a YouTube
declares full-service READY. Periodic checks/state/status/reload/independent retry
and generic PID1 BLOCKED foundations now have narrow remote fault acceptance;
unlike the earlier check-only run, this monitor ran without SIGSTOP.
Use `managed monitor --resource-config FILE`, or PID1 environment
`ZAPRET_AUTOTUNE_RESOURCE_CONFIG`; `managed resource-status` reads that same env
source. See [RESOURCE_MONITOR.md](RESOURCE_MONITOR.md) for ownership and repair.
HEALTHY is CHECKS_ONLY, not automatic strategy assignment. Generic strategy DB,
domain qualification matrix, runtime coverage/profile-group rendering and apply,
plugins/autotuning, maximum strategy collection and Prometheus remain TODO.
Three-CDN discovery/qualification is a YouTube
adapter contract, not a universal arbitrary-service requirement.
## Managed DoH live acceptance (2026-10-13): DNS verified, NOT READY