refactor: execute adapter plans through shared core

Execute the private YouTube qualification plan through core-owned scheduling while retaining worker cleanup, proof sealing and legacy policy boundaries. Preserve unsafe collector failures alongside concurrent cancellation or deadlines.

Send bounded Player JSON through stdin instead of argv and update all shared runner callers. Generic controller cutover and remote runtime acceptance remain pending.

Co-authored-by: GPT-6 <gpt-6@openai.com>
This commit is contained in:
ZeusinaandGPT-6 Bot committed 2026-10-15 17:25:12 +03:00
1 parent f4853173b3
commit e270810f33
24 files changed
+725 -92

No files matched your search

+7 -2
View File
@@ -37,8 +37,13 @@ qualify a candidate. V2 version/kind/expectations invalidate old HMAC rows/proof
historic v1 fingerprints remain unchanged. MP4 prefix health is not playback or
YouTube proof: three discovered CDNs, >=1024-byte producer samples, warmup,
suffix authorization and adaptive policy still belong to the legacy adapter.
Trusted compiled-in kind+version service modules remain a roadmap design, not an
implemented plugin API. Local source/closure review and injected-wire checks are
The private compiled-in YouTube module and core `executeAdapterPlan[T]` bridge
now drive the existing owned qualifier's ordered warmup and steady collection.
They do not add public module configuration or change this monitor's schemas,
controller, suffix authorization or legacy SOCKS5h routing boundary. Generic
controller cutover still needs dynamic-inventory fingerprints and warmup-bearing
generic proof binding; images/avatars and full YouTube READY remain unresolved.
Local source/closure review and injected-wire checks are
recorded alongside scoped managed v2 field observations below; full acceptance
is not implied.