docs: record scoped managed v2 verification

Record bounded typed qualification, apply, monitor fault/repair and dated independent cleanup; retain body/live-FD and untested v1/YouTube acceptance limits. Keep adapter registry and version-bound module migration explicitly future work.

Co-authored-by: GPT-6 <gpt-6@openai.com>
This commit is contained in:
ZeusinaandGPT-6 Bot committed 2026-10-15 15:33:26 +03:00
1 parent cd05e75189
commit d324b4137b
2 files changed
+114 -7

No files matched your search

+76 -4
View File
@@ -1,6 +1,6 @@
# Resource compatibility planner and isolated qualifier
## First collector migration (shared-core parity verified; managed acceptance pending)
## First collector migration (shared-core parity verified; managed v2 scoped observations)
Private typed response contracts now select generic GET/HEAD, full decoded image,
or bounded MP4 range validation inside the existing shared HTTPS transfer core.
@@ -63,7 +63,7 @@ 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.
### Public typed checks (v2; remote acceptance pending)
### Public typed checks (v2; scoped managed field verification)
`resource-check-v2.example.json` adds closed `kind` values `http`, `image` and
`mp4_range`; omitted v2 kind canonicalizes to `http`. V1 still requires explicit
@@ -99,9 +99,80 @@ 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 plugin framework, legacy deletion or full controller/journal/profile migration
is implied. Full runtime acceptance is pending; avatars and legacy exit78 remain
is implied. Full runtime acceptance remains incomplete; avatars and legacy exit78 remain
unresolved. No production READY claim.
### Managed v2 SCOPED_PASS observations (2026-10-15)
Source `cd05e75189f90c32e1346536c50f0973e7105cb3`. Privileged reads of
`/home/agent/managed-v2-cd05e75-20261015/report.md` and
`field-private/independent-audit.safe.json` record independent closeout at
**2026-10-15T12:28:52Z**, verdict **SCOPED_PASS**, with
`runtime_state_changed_by_audit: false`. These are bounded positive observations,
not unequivocal whole-criterion acceptance, full safety or READY. The static test
binary/image is not a deployment to the user's working SS service. The audit
matched 137 archived product files and the pinned native NFQ engine (1.0.2).
- Official public v2 CLI under owned PID1 SS/DoH exercised PNG/JPEG full decode
and video/mp4 + audio/mp4 bounded prefixes, each over TLS1.2/1.3 with verified
fixture CA/SNI. Two candidates × four resources × both TLS versions produced
16 M=3 cells / 48 real qualification TLS transfers. Queue-200 worker argv and
PID/start matched; exact-payload registry/matrix HMACs, v2 source and semantic
row fingerprints were independently recomputed, not imported PASS evidence.
- Official apply reused that proof without requalification: queue 300, canonical
`multidisorder`, three exact fixture hosts, journal v4 / generation 1 / committed
generic. Eight actual typed apply checks and eight initial monitor checks passed.
Source fingerprint:
`cc5a2622133daed58df0b2c22254f6112a3d9da7fbd9391ce7d1c6f467761886`;
committed config SHA-256:
`27f9a8ffd56a4c19d4bd522dd9f5a5e8b49b18b0ae48d41431ef9b22975ea772`.
- Five authenticated monitor snapshots (including initial state) showed truncated
PNG and overflowing video MP4 Content-Range each degrading **only** its affected
row to `DEGRADED / expectation_failed`, then repair restoring all four HEALTHY.
Host fixture changes produced real responses; controller PID 379/start 62777447,
journal/config/proofs/key/input hashes stayed the same, without requalification.
Apply/monitor wire evidence totals 48 transfers (33 healthy-mode, 7 PNG-fault,
8 MP4-fault); fixture timing/size/status is not durable product DTO telemetry.
- Dated closeout independently rechecked both official target stops exited 0;
all five recorded owned containers, owned network and 174 recorded PID/start
identities/namespaces were absent. Three foreign raw Docker inspect snapshots
remained byte-identical: `f6c9d42858e1` running, `4ad54175a54c` and `8cc36c813d6f`
stopped. Historical Xray inventory equality is a harness assertion only: its
initial raw process inventory was not retained, so it is not independently proved.
**Evidence limits:** production strict validation, authenticated outcomes and actual
fixture metadata establish this scoped typed-response observation. Bodies were
intentionally not retained to avoid data exposure and were **not independently
re-decoded**. Actual PID/start/parent/netns/native argv were independently checked;
live executable/held-FD snapshots were **not retained**. ACK/snapshot guards are
reviewed code/log enforcement, not a durable live-FD certificate. These missing
body/live-FD certificates prevent an unqualified full acceptance claim.
The initial observer misclassified the intentionally live DoH forwarder as an
unjoined worker. Original logs/harness remain; the corrected continuation used
the SAME proof, with no new qualification. This is a harness assertion correction,
not an observed product bug.
**NOT RUN in this field campaign:** public v1 managed GET/HEAD (86 current/old
local parity cases passed, not a remote v1 run); negative M3 qualification,
cancellation, freshness/24h expiry or old-matrix rejection; actual YouTube
discovery/three-CDN, suffix authorization, adaptive learning, warmup, avatar or
playback. New kind/version cannot promote old proofs by local unit coverage,
not a fresh remote rejection campaign. MP4 proves a prefix, not playback or an
exact 64-KiB body; public GIF remains deferred and legacy GIF retained. Prior full
Go/race/Python results are recorded above, not rerun for this docs-only change.
**Next minimum slice (design, NOT implemented):** a real YouTube/core adapter
boundary wrapping existing discovery and strict qualification calls, not a full
framework. Core owns networking, limits, proof, persistence and apply; YouTube
owns fresh URLs, three-CDN warmup/sampling, per-host adaptive learning and explicit
suffix policy. Plan a minimal compiled-in Go registry keyed by kind + version,
fail closed for unknown contracts; bind module/policy version into source/proof
and preserve authenticated historical restore under its original contract. No
dynamic plugin/RPC API exists. Do not generalize public POST/discovery until an
actual adapter needs that request contract. Retain legacy functionality until
parity and the remaining acceptance gaps are closed before full adapter cutover.
`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).
@@ -471,7 +542,8 @@ and `standaloneprivilegedaudit.safe.json`, dated `1792054235151`
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.
image/media capability above; owned managed v2 scoped observations are recorded
above, with full runtime acceptance still incomplete.
New-batch/versioned stores, uninterrupted rotation, strategy breadth and Prometheus
are separate future work, not prerequisites to documenting this collector slice.