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

+48
View File
@@ -707,6 +707,54 @@ Player media parsing (`playerMediaResource`) and owned native qualification
representative selection remain in the legacy controller; signed MP4 freshness
and the host/TLS qualification plan are pure service semantics in the module.
The next private execution bridge is now wired: `verifyGooglevideo` runs the
actual owned-worker collector through `executeAdapterPlan[T]`. Core independently
pins the known module binding and exact three-host/TLS1.2+1.3, 10-attempt/120-second
warmup, three steady samples/protocol and 1024-byte policy before worker startup
and probes. Invalid, duplicate, overflowing or weakened plans fail closed. The
executor preserves host order, alternating warmups, discarded learning successes,
strict measured steady facts and negative/fatal classification. It has no worker,
goroutine, persistence or seal capability; existing core range/ftyp/TLS validation
and post-worker-join proof validation/sealing remain the authority.
This is a **private execution bridge**, not public adapter configuration or a new
generic service/matrix proof. Dynamic-inventory fingerprints and warmup-bearing
generic proof binding are still required before generic-controller cutover.
The inherited legacy SOCKS5h boundary below is unchanged, not an all-DNS-answer
pinning guarantee. Three-CDN qualification does not itself grant suffix scope;
images/avatars and runtime acceptance remain separate and not READY.
Player JSON now travels through bounded private stdin (`curl --json @-`), not
process argv; the shared runner passes no stdin for metadata GETs. Video IDs are
validated before execution, POST bytes and headers remain unchanged, and opaque
public errors retain typed cancellation/unsafe-output causes. This is a private
Player transport change, not generic public POST/discovery configuration.
Bridge-local checks: an unchanged fixture run against archived `f485317` and the
wired producer has normalized proof SHA256
`fb380324e320a78f1ceb011c59b82b9de4ff4f31f5f032f469a181292987e3b2`.
Only warmup duration, attestation time and private seals are excluded; exact
probe order and cleanup/join are checked. Baseline and focused serial/race logs:
`/tmp/opencode/adapter-executor-{baseline,focused}.log`. These are injected local
checks, not network/native acceptance or a full-suite rerun.
Cancellation review follow-up: both warmup and steady probe boundaries now use
`managedRecoveryContextError`, preserving concurrent unsafe I/O/output overflow
alongside cancellation/deadline causes. Production collector regressions check
fatal/non-restartable classification, full cleanup/join and no attestation/seal;
plain cancellation remains timeout-safe. A pre-fix Go-overlay negative control
fails all eight mixed-failure cases; the fixed producer retains the hash above.
Actual `sudo` EUID-0 serial full Go checks passed (1806 test/subtest pass events),
as did 227 affected serial/race events, separate module race tests, vet and a
CGO-disabled build. Logs: `/tmp/opencode/adapter-executor-root-full.json`,
`adapter-executor-context-root-race.json`, `adapter-executor-context-focused.log`
and `adapter-executor-context-negative-control.log` in that same directory.
The reviewer-reported earlier `SavedFirstAndFailClosed/nonpass` freshness failure
did not recur in ten focused repeats or this full run; no freshness guards or
fixtures were changed, and its earlier cause is not established as a baseline
flake. Python checks were not rerun in this follow-up. These are local tests,
not remote runtime acceptance, a commit/deployment or a READY claim.
Core origin/TLS validation, shared image/media transfer code, bounded worker
lifecycle and post-cleanup/join sealing remain authoritative. Legacy media and
metadata routing retains SOCKS5h with the owned encrypted-resolver guard and