feat: discover and qualify Googlevideo CDNs autonomously
Retain strict three-host native qualification, discover fresh representative inventory automatically, and recheck deployed media before promotion. Document offline-only verification and outstanding field gates. Co-authored-by: GPT-6 <gpt-6@openai.com>
This commit is contained in:
1 parent
9984f21466
commit
3fc8563995
22 files changed
+798
-105
No files matched your search
@@ -1,5 +1,38 @@
|
||||
# Fresh managed-test target contract (isolated acceptance, not production approval)
|
||||
|
||||
## Autonomous three-CDN source candidate (2026-10-13): field acceptance pending
|
||||
|
||||
The user's three-CDN requirement is retained; the proposed single-CDN relaxation
|
||||
was withdrawn. Service-mode discovery needs no manual domains: missing/empty
|
||||
`ZAPRET_AUTOTUNE_GOOGLEVIDEO_VIDEO_IDS` uses primary `ZAPRET_AUTOTUNE_VIDEO_ID`
|
||||
(default `dQw4w9WgXcQ`) plus `aqz-KE-bpKQ` and `jNQXAC9IVRw`, deduplicated.
|
||||
A nonempty JSON array of 1..5 unique VideoIDs overrides this inventory. VideoIDs
|
||||
are discovery inputs, not proof of distinct CDNs.
|
||||
|
||||
Fresh round-robin Player requests are bounded to three rounds (at most 15 requests)
|
||||
and three minutes. Qualification selects three actual signed MP4 media hosts,
|
||||
with at least two roots and two prefixes, and twenty-minute remaining URL TTL.
|
||||
Only the existing version-1 owned native proof factory authorizes qualification:
|
||||
post-warmup actual media 3/3 on both TLS protocols for each measured endpoint.
|
||||
The common `googlevideo.com` suffix is an authorized extrapolative scope, not
|
||||
measured evidence for every Googlevideo host or cold/uniform behavior.
|
||||
|
||||
Experimental promotion uses the same proof and fresh deployed three-host media
|
||||
checks before committing apply. Insufficient inventory preserves the current
|
||||
experiment and uses configured retry cooldown; genuine exhausted strategy search
|
||||
still waits at least two hours. Qualified frontend is required; avatar success
|
||||
does not block this media stage, but whole-service health remains DEGRADED until
|
||||
actual avatar checks pass. Legacy service-off/exact-host behavior is unchanged.
|
||||
|
||||
This source candidate has only offline unit/fixture verification, not a newly
|
||||
deployed image or field-qualified autonomous promotion. The 2026-10-12 measured
|
||||
results below remain historical exact-endpoint evidence. Build from the committed
|
||||
source archive and field-test the owned factory, three actual CDNs, deployed
|
||||
relearning/apply, rollback and whole-service health before acceptance. Maximum
|
||||
strategy collection 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).
|
||||
|
||||
`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
|
||||
these commands. A role env or CLI-created identity is not enough. Provisioning
|
||||
|
||||
Reference in new issue
Block a user