feat: add typed generic image and MP4 checks

Preserve strict v1 semantics and fingerprints; bind v2 typed expectations to a new proof namespace. Reuse bounded shared collection across checks, monitoring, qualification and apply health. Document prefix-only MP4 and deferred public GIF/plugin/runtime boundaries.

Co-authored-by: GPT-6 <gpt-6@openai.com>
This commit is contained in:
ZeusinaandGPT-6 Bot committed 2026-10-15 15:07:54 +03:00
1 parent 9ab9fd73a9
commit cd05e75189
8 files changed
+654 -24

No files matched your search

+32 -5
View File
@@ -63,15 +63,42 @@ no owned containers/networks were created. Root-private artifacts, keys, manifes
and hashes remain retained. Selected foreign identity/running/start facts matched
before/after, not arbitrary foreign application-data hashes.
### Next minimal generic capability (not implemented)
### Public typed checks (v2; remote acceptance pending)
Add versioned declarative typed image/media expectations and validators for full
decoded bodies and strict Range proof; do not change v1 GET/HEAD semantics. Then
let the YouTube adapter supply qualified exact endpoints/dynamic inventory into
`resource-check-v2.example.json` adds closed `kind` values `http`, `image` and
`mp4_range`; omitted v2 kind canonicalizes to `http`. V1 still requires explicit
`http` and retains its serialization/fingerprints. V2 requires explicit statuses,
content_type, min_bytes and max_bytes. HTTP retains GET/HEAD semantics; typed
checks require GET. Image requires exactly [200] and image/png or image/jpeg,
full decoding, positive dimensions at most 16 MiPixels and a configured body
ceiling at most 5 MiB. Public GIF/omitted image MIME are deliberately deferred
until a decoder with an aggregate frame/pixel budget exists; legacy GIF remains.
MP4 requires exactly [206], video/mp4 or audio/mp4, and 16 <= min <= max <= 65536.
The core always requests bytes 0-65535, even with a smaller max_bytes; actual
returned bytes must fit that smaller bound and the validated Content-Range/ftyp.
This proves a bounded MP4 prefix, **not playback or YouTube qualification**.
All kinds use configured 100–30000 ms timeouts and byte ceilings, private stdin,
strict framing/TLS/origin and all-answer DNS policy through the same public check,
periodic monitor, isolated M=3 qualifier and apply-health path. Wire-valid typed
semantic failures are complete expectation negatives; unsafe output, malformed
metrics/framing, cancellation and ownership failures cannot become benign proof.
V2 source and row HMACs bind version, normalized kind and expectations, so old
plain-HTTP evidence/state cannot promote typed checks. V1 historical journal
reconstruction is unchanged. No public proof import or module framework exists.
Local verification for this v2 slice: full Go tests (`-p 1 -parallel 1`), affected
resource race tests, vet, CGO-disabled build, four managed-target Python fixtures
and shell syntax passed. Current and archived `45d28e3` each passed the existing
86 legacy adapter/generic-mismatch parity subtests. Privileged tests ran as EUID 0
inside the current user namespace (UID 0 maps to host UID 100000), not host-initial
root. These are local injected-wire/fixture results, not remote network acceptance.
Next let the YouTube adapter supply qualified exact endpoints/dynamic inventory into
the generic registry, preserving fresh discovery and the three-CDN contract.
Keep measured endpoint proof separate from explicit suffix/adaptive-learning
authorization: both capabilities are prerequisites to complete managed migration.
No proposal framework, legacy deletion or full controller/journal/profile migration
No plugin framework, legacy deletion or full controller/journal/profile migration
is implied. Full runtime acceptance is pending; avatars and legacy exit78 remain
unresolved. No production READY claim.