docs: record declarative resource-check acceptance

Co-authored-by: GPT-6 <noreply@openai.com>
This commit is contained in:
ZeusinaandGPT-6 committed 2026-10-13 19:47:25 +03:00
1 parent 4d7c4b33c3
commit cfce8170d7
2 files changed
+58 -5

No files matched your search

+47 -2
View File
@@ -1,5 +1,49 @@
# Fresh managed-test target contract (isolated acceptance, not production approval)
## Declarative HTTPS resource checks v1 (check-only)
Inside the provisioned owned managed target, with the tracked example available:
```sh
zapret-autotune check --config resource-check.example.json
```
This is not a standalone host checker for arbitrary external proxies: owned-target,
SS and configured wire-DNS readiness/ownership guards must pass before probes.
Version1 supports `kind: http`, GET/HEAD on HTTPS **DNS-hostname** URLs,
TLS1.2/1.3/both, timeout and expected HTTP statuses, MIME content type and
minimum/maximum bytes. Outcomes identify stable configured service/resource IDs
and report HTTP status, bytes and latency. URL/header secrets come from env via
private stdin, not argv; keep the config and env private when sensitive.
All resolved IPs are policy-checked before numeric CONNECT pinning; TLS verifies
the original hostname/SNI. Redirects and system-DNS fallback are forbidden.
Private destinations require explicit opt-in **and** CIDR restriction. IPv6
literal URLs and address failover are not supported in v1. Image/media decoding,
Range and suffix-scope qualification are not generic HTTP-check features.
Schema/loader and executable checks have unit and isolated remote acceptance for
source `4d7c4b33c36186d43ea89fd24354b1834b21692c`, image
`sha256:be5a1c45c6d40b390a29bfc9a5ab3975c3a8e0c015b98a524696312807dad9a4`.
The orchestrator supplied verified private evidence, not reread by this docs-only
update; see [PROGRESS.md](PROGRESS.md) for gates and cleanup. The positive private
TLS fixture trusted a **staging-only test CA**, never bypassed TLS or changed
production CAs. The existing DNS backend and earlier DoH outage evidence are reused,
not a new DoH implementation or new outage test here.
**Acceptance scope:** staging YouTube monitoring was SIGSTOP-isolated from checks,
then SIGCONT-resumed before graceful stop (exit0, owned cleanup, foreign baseline
unchanged). A prior managed monitor exit78 remains a runtime caveat, not proof of
whole-controller resilience. LIVE11082 was already stopped, not upgraded/restarted;
old SS1080/Xray were untouched. Historical LIVE observations below are not current
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
adapter contract, not a universal arbitrary-service requirement.
## Managed DoH live acceptance (2026-10-13): DNS verified, NOT READY
Supplied verified reports bind source `544dda7c85965fc3200de3af17fca9ef9999b2ce`
@@ -95,8 +139,9 @@ whole-service/avatar acceptance remains open. The 2026-10-12 measured results
below are historical, not the new factory evidence. New images still require
their own source/image binding and guarded apply/rollback acceptance. Maximum
strategy collection/search diversity and PID1 global-failure stay-alive remain unfinished future
increments. Arbitrary declarative service configuration is future work; no new
generic policy framework is supplied. See [GOOGLEVIDEO_DISCOVERY.md](GOOGLEVIDEO_DISCOVERY.md).
increments. Declarative check-only configuration is accepted above; generic
controller integration remains future work. No new generic policy framework is
supplied. See [GOOGLEVIDEO_DISCOVERY.md](GOOGLEVIDEO_DISCOVERY.md).
`managed init|reconcile|status|active-ids|apply` is exclusively for a **new dedicated container**
which owns its entire config. The existing/dev/production container must refuse