docs: record shared-core parity and rotation fault checks

Record scoped real-curl parity separately from older generic rotation fault evidence and pending managed runtime acceptance. Preserve strict YouTube qualification, refusal attribution limits and the next typed generic image/media capability.

Co-authored-by: GPT-6 <gpt-6@openai.com>
This commit is contained in:
ZeusinaandGPT-6 Bot committed 2026-10-15 12:17:00 +03:00
1 parent 45d28e3733
commit 9ab9fd73a9
1 file changed
+98 -17
+98 -17
View File
@@ -1,6 +1,6 @@
# Resource compatibility planner and isolated qualifier
## First collector migration (locally verified/reviewed; remote acceptance pending)
## First collector migration (shared-core parity verified; managed 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.
@@ -19,11 +19,61 @@ size requirement). The core accepts validated 16–65536-byte ranges; the existi
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.
This is collector migration only: public schemas and the legacy YouTube producer
remain unchanged, including three discovered CDNs, adaptive A/E, warmup then 3/3
samples on each TLS version, explicit googlevideo.com suffix authorization, fresh
discovery, and independent qualification of image/avatar assets. The legacy path
is retained. Generic GET success is never full YouTube qualification.
Recorded local verification: archived `2149a4a` versus current source passed 86
parity subcases; 14 new integration cases, 11 focused EUID-0 serial/race tests and
full Go tests passed (full Go about 55s). Python static/config/startup checks passed;
the long supervision check timed out at 18s and again at 120s and is unresolved.
Do not call all tests green or infer a regression from that timeout: entrypoint
code was unchanged and later full Go entry tests passed. These are prior results,
not reruns in this docs-only update.
### Scoped remote shared-core parity (2026-10-15)
Privileged-read evidence: `/home/agent/core-runtime-parity-45d28e3-20261015/report.md`.
Exact-source baseline `2149a4a` and current
`45d28e37330069ddf0efa3120fec8a558d37ba7f` each passed 48 real curl/HTTPS/SOCKS5h
fixture subtests (24 cases × TLS1.2/1.3). Of the normalized rows, 46 matched and
two intentionally differed: overflowing Content-Range total, formerly saturated
by ParseInt, now rejects without a PASS DTO. Known negative classifications are
preserved; invalid/unknown/overflow totals are not proof.
Coverage includes GET/HEAD expectations and retained mismatch facts, bounds,
redirect/framing/trust rejection, real PNG/JPEG/GIF decode and rejection, strict
206 range/ftyp checks, and stdin/argv/result privacy sentinels. Real 65536-byte
and 1024-byte media responses passed the same Range request. Each version made
60 SOCKS5h connections/SNI handshakes and 58 authenticated HTTP requests, including
18 actual Range requests; two untrusted-certificate attempts stopped before HTTP.
Original hostname/SNI was retained; curl verified a fresh private fixture CA,
without TLS bypass. Timing/speed were positive but excluded from exact normalized
parity hashes; this is not a performance comparison or fatal-reason-tree parity.
The proxy maps only allowlisted fixture names to a loopback TLS listener: it is
not an SS proxy or DoH resolver. **NOT RUN:** normal public CLI under owned PID1
SS/DoH, managed ownership/guard checks and probe orchestration, NFQ/native behavior,
real YouTube discovery/three-CDN qualification, or candidate/apply/monitor flow.
No DoH validation or production qualification follows from helper tests. No
candidate/PASS/DB/JSON proof imports occurred. Helpers exited and joined listeners;
no owned containers/networks were created. Root-private artifacts, keys, manifests
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)
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
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
is implied. Full runtime acceptance is pending; avatars and legacy exit78 remain
unresolved. No production READY claim.
`plan` remains **proposal-only** and never changes runtime or config.
Explicit generic startup apply/replay and the per-PID-1 failure latch have passed
@@ -349,23 +399,54 @@ generation 1 → selected multisplit B generation 2 → identical B replay gener
- The first independent forensic audit passed the bounded 14-HMAC positive evidence,
but the automated grader rejected missing independently refreshed dated evidence
and exact native argv phase paths. Do not upgrade this to full native/safety
acceptance. Unknown-ID remote rejection was **NOT RUN** (unit coverage exists);
full rotation fault/crash/old-profile rollback was **NOT RUN**. Natural 24-hour
expiry remains unit-only, without a 24-hour wait.
acceptance. Unknown-ID refusal and old-profile fault/repair observations were
subsequently recorded below, with narrower attribution than a branch-specific
refusal proof. Crash safety remains untested. Natural 24-hour expiry remains
unit-only, without a 24-hour wait.
- Prior local verification recorded 17 EUID-0 fixtures in one race/parallel pass
with 57 subrecords; namespace UID 0 mapped to host UID 100000, not host-initial
root. Full producer Go/race and four Python checks passed serially after parallel
resource-contention failures; this does not establish a contention-free baseline.
These are prior checks, not tests rerun for this documentation-only update.
**Next critical P0 gate:** remote rotation health failure must restore the OLD
generic policy/ref and bytes; failed rollback health must retain prepared state,
then repair-only reconciliation must recover the old profile, never promote pending.
Also run unknown-ID rejection against a fresh required baseline. Do not substitute
another positive generation sequence for these missing gates. Startup remains
one-shot per PID 1, without automatic apply retry. New-batch/versioned stores,
uninterrupted rotation, broader bounded strategy collection and Prometheus remain
future work, in that roadmap order.
### Subsequent old-generic rotation faults (bounded saved-artifact acceptance)
Actual remote source was `8d43dd9`, **not** shared-core `45d28e3`; these separate
results do not establish end-to-end acceptance of a combined release. Privileged
reads verified `/home/agent/rotation-fault-8d43dd9/field-private/ACCEPTANCE.safe.md`
and `standaloneprivilegedaudit.safe.json`, dated `1792054235151`
(2026-10-15 08:50:35.151 UTC), verdict
`PASS_BOUNDED_SAVED_ARTIFACTS_AND_CURRENT_CLEANUP`.
- All 13 snapshots passed exact-serialized-payload HMAC/immutable proof checks.
Old A is generic with empty/default policy, not baseline; B selects multisplit.
Historical old/new refs reconstruct independently.
- One-shot: eight B apply checks (one HTTP500), eight successful A rollback checks,
A committed/pending clear, no automatic reapply through 80s; official stop0.
- Persistent: 24 checks across apply/rollback/cleanup reconciliation, three
HTTP500; A bytes physically restored with PREPARED old-A/pending-B retained,
no reapply through 80s; stop78 retained the unsafe-cleanup latch. Healthy fixture
plus only APPLY=1→0 (requested B still set) gave eight reconcile + eight monitor
successes, old A committed/pending clear and four HEALTHY resources; stop0.
- Total: 56 authenticated requests, TLS28/28, four controlled HTTP500. At the
dated audit all 150 recorded owned PID/start identities were gone, recorded netns
had no processes, five owned containers and network were removed, and three
foreign raw-inspect hashes were unchanged. Root-private evidence was retained;
sampled identities are not an exhaustive all-helper inventory.
- Valid-syntax `unknown-safe-id` reached the actual CLI apply entry, which exited
78 and latched BLOCKED, with zero requests. Before/stopped config, journal,
backup and proof bytes were unchanged; no staging was sampled. This is an
**observed refusal with an unknown-ID request**, not uniquely attributed to the
unknown-ID branch: the generic diagnostic cannot exclude another trust error.
Source validation order supports an inference, not a specific logged reason
or complete pre-mutation proof. Official stop0 is separate from CLI exit78.
Startup remains one-shot per PID1, without automatic apply retry. These fixture
faults do not establish crash/cancellation safety, continuously live rotation,
causal DPI benefit or READY. Next migration work is the minimal typed generic
image/media capability above; owned managed runtime acceptance remains pending.
New-batch/versioned stores, uninterrupted rotation, strategy breadth and Prometheus
are separate future work, not prerequisites to documenting this collector slice.
## Bounded generic apply/replay and failure-latch acceptance