Files
zapret-autotune/internal/adapter/youtube
ZeusinaandGPT-6 Bot f4853173b3 feat: extract versioned YouTube service adapter
Wire pure Player parsing and strict qualification planning through a compiled-in kind/version registry. Fail closed before discovery requests when the required module is absent or mismatched.

Require sealed module-bound v2 evidence for new writes while preserving fresh trusted v1 apply eligibility and historical rollback. Keep legacy SOCKS5h routing, separate suffix/asset policy and public configuration unchanged; generic controller cutover and field acceptance remain pending.

Co-authored-by: GPT-6 <gpt-6@openai.com>
2026-10-15 16:23:54 +03:00
..

Internal YouTube adapter

The compiled-in youtube/1 module parses bounded Player JSON and supplies the ordinary signed MP4 qualification policy and ordered host/TLS sample plan. The existing YouTube execution paths select it explicitly through the core's kind/version registry. Unsupported or absent modules fail closed.

The core retains origin validation, HTTPS/SNI/certificate checks, transport framing/body bounds, retries/cancellation, worker ownership, cleanup/join and proof sealing. Module output is not evidence or permission to claim PASS. Signed URLs remain ephemeral and cannot serialize through the internal contract.

New adaptive proof v2 binds the module kind, version and immutable policy digest inside its producer seal. Unbound proof v1 explicitly means the historical YouTube v1 policy: fresh trusted stored proofs retain their original apply eligibility; expired proofs reconstruct history but cannot authorize fresh apply. Only new producer/persistence writes require sealed module-bound v2 evidence. Cold historical evidence is unchanged. Discovery entrypoints preflight the module before requests; absence/mismatched identity or policy is a fatal configuration failure, not unavailable inventory or a no-strategy cooldown.

Legacy routing remains SOCKS5h with encrypted-resolver ownership guards and origin/SNI/certificate/TLS checks, not generic all-answer approval/IP pinning. Full request-policy capabilities and parity are prerequisites to generic cutover.

This is a real internal legacy-execution integration, not a fully generic controller, public v3 configuration, native addon, runtime plugin or readiness claim. Another compiled-in module can implement the closed internal contract; public GET/HEAD v1/v2 configuration remains unchanged.