diff --git a/PROGRESS.md b/PROGRESS.md index bb25bdd..2bd10c0 100644 --- a/PROGRESS.md +++ b/PROGRESS.md @@ -1,9 +1,26 @@ # Прогресс реализации -Срез на **2026-10-11**. Этот файл описывает фактическое состояние кода, а не весь объём требований из `Requirements.md` и `Architecture.md`. +Срез на **2026-10-12**. Этот файл описывает фактическое состояние кода, а не весь объём требований из `Requirements.md` и `Architecture.md`. ## Текущий статус +### Googlevideo suffix RC — browser-verified experiment (2026-10-12) + +- Source RC `eade051c2bc335b71b1616d697326ca4c8019d70`, immutable image `sha256:fdb60593e29d7c337a413a47aaddfbcaaeabdeb877042c58f506d4abdc98a13b`, isolated host SOCKS `127.0.0.1:11082`. Recorded journal: generation3, active candidates [1,2,3], scope `experimental_googlevideo_suffix`; `www.youtube.com` and `i.ytimg.com` profiles preserved. Older targets were unchanged. These are recorded field observations, not a new probe/deployment by this documentation commit; its SHA is not the tested image source. +- Fresh signed media on `rr16---sn-n8v7znsz.googlevideo.com` returned HTTP206, 65536 bytes, MP4 `ftyp`, TLS1.2. On **2026-10-12 the user confirmed browser videos work** with this live RC and accepted one shared profile for Googlevideo, including initial learning. Browser images also appeared, but that does not qualify every image route. +- One suffix profile is a **composite native circular A/E profile with two strategies and per-host learning**, not one uniform static strategy. Explicit operator experimental policy is durable across restart with hash/rollback guards; it is neither family-qualified nor `READY`, and no all-host cold 3/3 result is claimed. +- Service health already checks actual fresh image resources and media with both TLS protocols. Experimental recovery intentionally returns without automatically qualifying or replacing the operator-approved experiment: the remaining gap is autonomous experimental recovery/autoqualification, not missing probe implementation. Operator scope coverage and qualification are separate states. + +Remaining acceptance gates (not asserted defects): + +1. Representative fresh signed media evidence: at least three unique hosts across at least two roots/prefixes, post-warmup 3/3 for both TLS protocols plus actual media transfer. Do not impose uniform static/cold behavior on the accepted learning experiment or label it normally qualified without evidence. +2. Qualify the avatar route/profile: only the thumbnail image profile is currently active; browser-visible images do not close this gate. +3. Field-accept actual restart/recreation recovery after the all-Googlevideo suffix change, including renewed native learning; older exact-host lifecycle PASS does not cover this RC. +4. Resolve autonomous recovery/autoqualification policy for the approved experiment without silently replacing or promoting its operator-approved scope. +5. Reconcile service status with those results: distinguish operator-covered suffix from unresolved qualification/assets; no family-qualified/`READY` or blanket production claim yet. + +### Earlier isolated-target acceptance (2026-10-11) + - **2026-10-11 clean RC acceptance — PASS:** source RC `d8316e695bc36e1243c111e19bb1e527355907b6`, tag `zapret-autotune-managed-target:rc-d8316e6`, immutable image `sha256:5636aa9031fd0f6a0513f2e22cc0c39b1c806e9714b7f9ac040c8713d6a26c6c`, built from the source git archive with pinned inputs. These source/image identifiers predate this documentation update; a later docs commit is not the tested image source. Private source root: `/home/agent/zapret2-autotune-rc-d8316e6`. Additional clean target root: `/home/agent/zapret2-managed-clean-d8316e6-45bb14ba`, Compose project `zapret-autotune-clean-d8316e6-45bb14ba`, SOCKS TCP/UDP `127.0.0.1:11081`; left running for inspection. The existing target on `11080` was not replaced. - **Clean bootstrap/evidence:** state was empty before launch (root-owned directory mode `0700`, independent 64-hex secret, `.env` mode `0600`); real `blockcheckw` binary, no mocks or copied config/candidates. Fresh init was observed, but fast bootstrap prevented capturing an exact generation-0 status snapshot. Generation2 committed frontend ID1 and GGC ID2 for exact `rr17---sn-n8v7kn7d.googlevideo.com`; both candidates have valid raw TLS1.2/TLS1.3 evidence, 3/3 each. Actual root config uses the verified layout-safe fake + multidisorder frontend seed. Periodic `lastProbeAt` advanced with failure counter0 and idle recovery. - **Clean lifecycle gates:** monitor SIGKILL changed host PID522765→525271 inside the same container/PID1, DockerRestartCount0; IDs[1,2] and config hash `57e639c98420be73a8ec4754b20ba975d81aced44215ed547b1ac029c89c14de` unchanged. Graceful stop exited0 in 0.61s, with no worker leaks. Forced recreation (`5af686e2ad94…`, host PID525625) preserved generation2/IDs/hash. Initial post-recreation failure counters1 then2 are historical observations with unproven cause: a fresh-discovery GGC mismatch sample does not prove the actual probe error cause. The next default probe at 07:54 reset the counter to0 with no active recovery. Player API OK and host SOCKS curl to `www.youtube.com` HTTP200; no media playback/SABR claim. diff --git a/deploy/managed-target/README.md b/deploy/managed-target/README.md index 88bc9e6..123f2d6 100644 --- a/deploy/managed-target/README.md +++ b/deploy/managed-target/README.md @@ -5,6 +5,35 @@ reconfigure, or stop the existing `zapret2-ss-autotune` container. The target starts from a disabled managed baseline; `managed monitor` bootstraps the frontend/API strategy, then discovers and applies an exact-host GGC strategy. +## Recorded Googlevideo suffix experiment (2026-10-12) + +Source RC `eade051c2bc335b71b1616d697326ca4c8019d70`, immutable image +`sha256:fdb60593e29d7c337a413a47aaddfbcaaeabdeb877042c58f506d4abdc98a13b`, +isolated SOCKS `127.0.0.1:11082`: recorded journal generation3, active [1,2,3], +scope `experimental_googlevideo_suffix`. Frontend `www.youtube.com` and +thumbnail `i.ytimg.com` profiles were preserved; older targets were unchanged. +These recorded observations predate this docs commit; no deployment or fresh +network check is implied here. + +Fresh signed media on `rr16---sn-n8v7znsz.googlevideo.com` returned HTTP206, +65536 bytes with MP4 `ftyp` over TLS1.2. The user confirmed browser videos work +on 2026-10-12 and accepts initial learning. The shared suffix profile is native +circular A/E: **two strategies with per-host learning**, not a single uniform +static strategy or proof of all-host cold 3/3. Its explicit operator experimental +policy persists across restart under hash/rollback guards, but is **not +family-qualified or READY**. Browser-visible images do not qualify the avatar +profile; only the thumbnail image profile is currently active. + +Service-mode health already probes fresh actual images and media using both TLS +protocols. Experimental recovery deliberately does not automatically qualify or +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. + ## Provisioning From this directory, create a private `.env` with a fresh independent password @@ -61,7 +90,8 @@ Adaptive qualification is **post-warmup**, distinct from cold qualification; initial connections may fail and native learning must repeat after restart. It requires at least **three real unique signed ordinary media host samples**. Three sample videos may all resolve to the same CDN host: that means -`DEGRADED`, no authorized googlevideo suffix, not fabricated coverage. Service +`DEGRADED`, no family-qualified googlevideo suffix, not fabricated coverage. The +explicit operator experiment above is separate from this qualification. Service asset checks cover sampled thumbnail/avatar routes, not the whole thumbnail pool. The current service/adaptive hardware acceptance gate is **pending**; the old clean-run PASS below does not qualify these new modes. @@ -144,9 +174,10 @@ bounds do not shorten the monitor's 90-minute bootstrap/recovery scan budget. SIGTERM/SIGINT cancels and waits for the monitor before stopping target-local zapret and Shadowsocks children. Nonretry monitor fatal exits stop the entrypoint; technical exits and Shadowsocks failures restart from private configs -only after safe cleanup. Monitor health is YouTube Player API status through the owned SOCKS, -not video playback/SABR; GGC candidates are scoped to the exact discovered -hostname. +only after safe cleanup. Legacy monitor health is YouTube Player API status +through the owned SOCKS, not video playback/SABR; legacy GGC candidates are scoped +to the exact discovered hostname. Opt-in service health also checks actual fresh +images and media; the experimental suffix scope above is not family qualification. ## Recorded clean-run acceptance (2026-10-11): PASS