docs: record final managed RC field acceptance and remaining gates

Record supplied fd25cb8 managed-image watch, representative post-warmup media transfers and degraded recovery continuation without claiming avatar or durable family qualification. Require explicit Dockerfile.target and positive entrypoint/marker checks before image promotion; preserve the user README badge.

Co-authored-by: GPT-6 <gpt-6@openai.com>
This commit is contained in:
ZeusinaandGPT-6 Bot committed 2026-10-12 23:34:38 +03:00
1 parent fd25cb8939
commit 9984f21466
3 files changed
+111 -24

No files matched your search

+55 -3
View File
@@ -7,6 +7,41 @@ frontend/API strategy, then discovers and applies an exact-host GGC strategy.
## Recorded Googlevideo suffix experiment (2026-10-12)
### Final field follow-up: DEGRADED / NOT READY
Supplied results for source `fd25cb89398300bb9849db4b5511af75bf86eccf`, correct
managed image `sha256:73e955e7fdc6efaef88c62ebe4f7afeab71c29d29ba3c88b2a2b7547bb647da5`,
container `a4e845a6d7…`, official managed PID 1 and SOCKS11082 supersede the
earlier pending media/fallback labels below. The `37823…` prototype is not active.
Watch `20:15:07.686Z` → `20:30:54.826Z` on 2026-10-12 completed over 15 minutes:
restart count0, monitor alive; a fresh post-report check returned SOCKS `0500`,
WWW HTTP200/SSLVerifyResult0. Native `socks5h` probes respect SS `-d 8.8.8.8`.
Post-warmup TLS1.2 and TLS1.3 each passed 3/3 on
`rr4---sn-axq7sn7z.googlevideo.com`, `rr5---sn-n8v7kn76.googlevideo.com`, and
`rr18---sn-axq7sn7z.googlevideo.com`: **18 actual HTTP206, 65536-byte MP4 `ftyp`
transfers**, valid Range `0..65535`. Initial warmup is separate: TLS1.2 three
timeouts, TLS1.3 three passes. No cold/all-host claim; the old rr5 `sn-ixh`
counterexample was not retested. Thumbnail JPEG decoding passed 3/3 per TLS
(2888 bytes, SSLVerifyResult0). Watch metadata found an allowed `yt3.ggpht.com`
avatar URL, but actual both-TLS avatar transfers returned curl28, zero samples.
There is no saved avatar evidence or qualified avatar profile.
Recovery now continued through validated peer-TLS/payload nonpasses with current
job-bound transaction/store/ownership guards: genuine no-qualified-strategy
cooldown advanced naturally while the monitor stayed alive, without a reset.
Snapshot generation9/IDs[1,3,9]/hash `0e34…`/experimental scope were unchanged;
candidate3 has no qualification/evidence. This is degraded recovery acceptance,
not successful avatar repair, durable family qualification or promotion.
Actual avatar transfer/strategy qualification and durable representative
multi-host family/mode qualification remain unfinished; automatic family
qualification is not implemented. Other targets on 1080/11080/11081 and Xray
were unchanged. No remote operations are performed by this docs update.
Private sanitized proof: `/home/agent/zapret2-autotune-rc-fd25cb8/proof/final.safe.json`.
Exact results and limits: [PROGRESS.md](../../PROGRESS.md).
### Historical initial experiment
Source RC `eade051c2bc335b71b1616d697326ca4c8019d70`, immutable image
`sha256:fdb60593e29d7c337a413a47aaddfbcaaeabdeb877042c58f506d4abdc98a13b`,
isolated SOCKS `127.0.0.1:11082`: recorded journal generation3, active [1,2,3],
@@ -30,9 +65,10 @@ replace this approved profile. Remaining acceptance is representative signed
media coverage (at least three hosts across two roots/prefixes, post-warmup 3/3
on both TLS protocols plus media), avatar qualification, actual restart/recreation
recovery of this suffix RC, and autonomous experimental recovery/autoqualification
policy with accurate covered-versus-qualified status. See
[PROGRESS.md](../../PROGRESS.md) for the five remaining gates. The older clean-run
PASS below does not close them.
policy with accurate covered-versus-qualified status. These were that initial
RC's pending gates; see the final follow-up above for later field results and
[PROGRESS.md](../../PROGRESS.md) for current remaining work. The older clean-run
PASS below does not close family/avatar qualification.
## Provisioning
@@ -67,6 +103,22 @@ in the private `.env` and pull that immutable image before starting the target.
Use a managed target image, not the generic image. Do not deploy production
with a tag or local default.
Build from the repository root with an explicit Dockerfile and assert the
image contract **before promotion**, even if its tag says managed-target:
```sh
IMAGE=zapret-autotune-managed-target:local
docker build --pull -f Dockerfile.target -t "$IMAGE" .
test "$(docker image inspect --format '{{json .Config.Entrypoint}}' "$IMAGE")" = '["/bin/sh","/opt/managed-target-entrypoint.sh"]'
docker run --rm --network none --entrypoint /bin/sh "$IMAGE" -ec 'test "$(cat /etc/zapret-autotune/target-id)" = zapret-autotune-managed-v1; test -f /opt/managed-target-entrypoint.sh'
```
Root `Dockerfile` is the proposal/prototype image, not the managed PID 1 service;
omitting `-f Dockerfile.target` previously produced a mistagged prototype.
These positive entrypoint/marker assertions do not replace live acceptance.
Promote the same immutable image as described in
[MANAGED_TARGET.md](../../MANAGED_TARGET.md#build-once-promote-the-same-image).
Offline static guard (from repository root):
`python3 deploy/managed-target/check_static.py`.
Offline real pre-launch validation and private Compose forwarding fixtures: