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:
ZeusinaandGPT-6 Bot committed 2026-10-13 10:12:10 +03:00
1 parent 9984f21466
commit 3fc8563995
22 files changed
+798 -105

No files matched your search

+34
View File
@@ -0,0 +1,34 @@
# Bounded representative Googlevideo discovery
The YouTube default inventory is the configured primary plus `aqz-KE-bpKQ` and
`jNQXAC9IVRw`, deduplicated. Explicit configured inventories override it. The
inventory (one to five IDs) is queried freshly
in round-robin order for up to three rounds, bounded by three minutes. No new
manual CDN addresses, host rewriting or IP pinning is added.
With only one configured video, diversity depends on that video's real Player
backend rotation; if it does not rotate, qualification remains unresolved.
Discovery deduplicates actual ordinary signed MP4 media hosts, refetches expired
inventory and selects three hosts passing the existing root/prefix diversity
gate. URLs need twenty minutes remaining for the three sequential owned native
warmups and verified TLS transfers. URLs stay transient; unresolved diagnostics
contain only attempt/host and rejection counts. Discovery is not media proof.
Production adaptive recovery uses this collector. Existing experimental suffixes
retain their one-host operational recheck; promotion requires fresh three-host
inventory and the unchanged version-1 owned native proof factory. Insufficient
inventory leaves the committed experimental profile intact and retries after
the configured cooldown, not the exhausted-strategy two-hour pause. Native GGC
scope requires qualified frontend and any supplied asset candidates remain
qualified and nonoverlapping; missing avatar inventory is not its prerequisite.
Apply checks frontend and all three actual media resources in the newly deployed
daemon, including bounded learning and three verified transfers per TLS version.
Whole-service monitoring still reports avatar degradation independently.
Single-CDN version-2 qualification has been withdrawn. Maximum strategy catalogs,
new video discovery sources and controller stay-alive changes are separate work.
The three-CDN requirement was reaffirmed on 2026-10-13. The common suffix remains
authorized extrapolative coverage; only exact measured endpoints have transfer
evidence. This candidate is offline unit/fixture-verified only: owned factory,
autonomous discovery/promotion and deployed learning still need a scoped actual
three-CDN field test. No remote network checks or deployment accompany this update.