refactor: share strict resource validation through generic core

Use private typed generic, image and MP4 response contracts in the existing bounded HTTPS execution pipeline. Preserve generic mismatch measurements, strict legacy DTOs and producer behavior; reject overflowing Content-Range integers before normalization.

Add injected-wire adapter parity and direct-core regressions. Local targeted EUID-0/race, full Go and config fixtures passed; native acceptance remains pending. The unrelated long Python supervision timeout remains unresolved. No public schema, suffix-learning or controller migration.

Co-authored-by: GPT-6 <gpt-6@openai.com>
This commit is contained in:
ZeusinaandGPT-6 Bot committed 2026-10-15 12:04:28 +03:00
1 parent 2149a4abc8
commit 45d28e3733
7 files changed
+439 -50

No files matched your search

+25
View File
@@ -1,5 +1,30 @@
# Resource compatibility planner and isolated qualifier
## First collector migration (locally verified/reviewed; remote acceptance pending)
Private typed response contracts now select generic GET/HEAD, full decoded image,
or bounded MP4 range validation inside the existing shared HTTPS transfer core.
The redundant legacy forwarding wrapper and media boolean are removed; image and
media adapters retain their measurements and GooglevideoPass DTOs. Generic v1
status/MIME/byte expectations use the same validation entry, with a distinct
completed-mismatch result retaining the same measured facts. No public Range config, schema,
proof importer, registry or dependency was added.
Injected-wire tests exercise the real generic producer and legacy callers, both
TLS versions, normalized byte/hash/timing facts, private stdin/pinning, origin,
redirect, framing, bounds and strict range/ftyp/image decoder rejection. Direct
core tests ensure strict validation is not an unused legacy-only helper.
MP4 requests use Range `0-65535` (a 64 KiB upper bound, not an exact response
size requirement). The core accepts validated 16–65536-byte ranges; the existing
producer additionally requires at least 1024 measured bytes. Content-Range end
and total must parse without overflow, with total greater than end; rejected or
unknown totals cannot produce a media PASS DTO.
This is collector migration only: legacy owned-worker production, three-CDN
sampling/warmup, native suffix adaptive learning and image/avatar readiness gates
remain unchanged. Generic matrix/controller/journal/profile replacement still
requires typed discovery/range proof and suffix/adaptive-learning capability parity.
No remote result, service READY or full controller migration is claimed here.
`plan` remains **proposal-only** and never changes runtime or config.
Explicit generic startup apply/replay and the per-PID-1 failure latch have passed
bounded remote acceptance with independent privileged verification (see below).