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:
1 parent
9ab9fd73a9
commit
cd05e75189
8 files changed
+654
-24
No files matched your search
+22
-2
@@ -1,6 +1,6 @@
|
||||
# Periodic configured resource checks
|
||||
|
||||
`managed monitor --resource-config FILE` runs resource-config v1 periodically.
|
||||
`managed monitor --resource-config FILE` runs resource-config v1 or v2 periodically.
|
||||
PID 1 selects the same mode when `ZAPRET_AUTOTUNE_RESOURCE_CONFIG` is nonempty;
|
||||
unset preserves the existing YouTube monitor. The modes share one singleton
|
||||
lock. Supply an absolute container-visible config path (for example mount a
|
||||
@@ -19,9 +19,29 @@ not playback health, generic recovery or whole-production READY: HEALTHY is
|
||||
base passed native full/race checks, independent security review and isolated
|
||||
remote fault acceptance for `4efc066` plus ownership-status fix `5c85f3f`.
|
||||
See [PROGRESS.md](PROGRESS.md) for supplied evidence and its narrow scope.
|
||||
Version1 is bounded to 16 services / 64 resources with stable configured IDs;
|
||||
Both versions are bounded to 16 services / 64 resources with stable configured IDs;
|
||||
valid configuration/state does not imply an automatic strategy assignment.
|
||||
|
||||
V1 remains HTTP GET/HEAD only, with explicit `kind: http`. See
|
||||
`resource-check-v2.example.json` for v2: omitted kind defaults to `http`; all
|
||||
expectations explicitly declare statuses/content_type/min_bytes/max_bytes.
|
||||
`image` is GET-only, [200], PNG/JPEG with full bounded decode (5 MiB maximum,
|
||||
16 MiPixels); public GIF is deferred pending an aggregate frame/pixel budget,
|
||||
without changing legacy GIF adapters. `mp4_range` is GET-only, [206], audio/mp4
|
||||
or video/mp4, 16–65536 bytes, checked Content-Range and ftyp. Range stays fixed
|
||||
at 0-65535; a smaller max_bytes bounds the actual response, not the requested end.
|
||||
Operator Range/Accept-Encoding headers remain forbidden in both versions.
|
||||
Timeouts (100–30000 ms) and declared byte limits apply to every kind. Typed
|
||||
wire-valid semantic failures degrade checks; malformed/unsafe execution cannot
|
||||
qualify a candidate. V2 version/kind/expectations invalidate old HMAC rows/proofs;
|
||||
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 v2 checks are covered by injected-wire tests;
|
||||
Independent local source/closure review passed; managed remote acceptance is
|
||||
still pending.
|
||||
|
||||
Invalid resource JSON initially or after reload is BLOCKED, with no DNS or
|
||||
transfers until repaired. Bad static target role, proxy or DNS settings still
|
||||
fail startup validation; resource JSON is deliberately not part of
|
||||
|
||||
Reference in new issue
Block a user