36 KiB
Прогресс реализации
Срез на 2026-10-11. Этот файл описывает фактическое состояние кода, а не весь объём требований из Requirements.md и Architecture.md.
Текущий статус
- 2026-10-11 container-owned control (pending working-tree changes): all technical child restart control belongs to the entrypoint/PID 1 inside the same container, not host systemd. Safe cleanup precedes each retry; three runtime starts per rolling six hours include the initial start, with cancellable 15s/30s backoff capped at 60s. Configuration/safety/DB/journal/rollback/cleanup failures and exhausted retry budget stop fail-closed. SIGTERM cancels and joins the monitor, restores safely, then stops target-local zapret and SS children. No additional dependency or host service installation is required. Compose keeps
restart: "no"to avoid safety loops and now allows 240s stop grace: 140s sequential cleanup including 45s monitor join, plus room for a deferred 45s startup command/kill grace and overhead. A fresh-shell join watchdog is cancelled promptly on child completion; graceful shutdown never needs its full timeout. Container-platform lifecycle and host-boot policy remain deployment-operator responsibilities. - 2026-10-11 strategy absence (pending working-tree changes): genuine validated no-qualified-strategy outcomes in bootstrap/recovery persist a wait of at least two hours in SQLite. Both fresh bootstrap and periodic recovery use the greater of two hours and the configured recovery cooldown, preserving longer settings. The same container continues light probes without scans/apply during the wait; startup respects the persisted expiry, and normal threshold-driven recovery resumes after expiry. Other ordinary outcomes keep the default 30m cooldown. Malformed reports/runner/safety errors are not absence. The separate 90-minute whole-job watchdog plus 30-second restoration reserve remains an abnormal technical ceiling, not a normal no-strategy result or the absence wait.
- Root operator docs now describe this contract, preserving immutable tagged/digest promotion, BuildKit/pinned builds, private
.env, whole stopped-state backup/restore and exact legacymanaged-testguards for a new isolated target only. No old target adoption or Xray changes. New runtime changes still need their owners' focused checks and isolated live acceptance (retry/backoff, SIGTERM, durable absence expiry/resume); this documentation update does not claim those checks were run.
История реализации (не текущие инструкции)
The dated facts below are historical snapshots. In particular, host-systemd unit installation/restart/start-limit guidance and its acceptance tests are superseded by container-owned control above; they impose no current deployment requirement. Earlier “not deployed/not verified” snapshots do not override later recorded isolated-target acceptance. Production acceptance of the new supervision/absence policy remains pending.
-
2026-10-11 production-candidate update (remote checks dated 2026-10-10 UTC):
ed4298dadds one 90-minute budget per managed bootstrap/recovery job, shared across phases. Watchdog expiration is abnormal/fatal, never ordinary nonpass/cooldown continuation; clean timeout permits technical exit 75 only after worker join and bounded 30-second restoration. Any guard/DB/rollback/cleanup or mixed unknown error vetoes restart (78); configuration errors use 64, graceful shutdown 0. Independent review reproduced and closed mixed-timeout, fatal-discovery and fatal-health/deadline races. Preferred frontend seed is now the layout-safe alternative verified in prior 60/60 requests; cached definitions are not rewritten. -
2026-10-10 restart/startup hardening: optional
deploy/managed-target/zapret-autotune.serviceuses foreground Compose, no blanket Docker restart, systemd allowlisted 75 with bounded starts (3 per 6h); shutdown grace 120s / unit stop budget 180s.61e6e00adds guarded fixed-DBmanaged reconcilebefore initial activation; init/reconcile/start are bounded (45/45/30s plus 5s kill grace), all startup refusals map to 78. Unknown state is not sourced even by cleanup. Actual systemd tests: technical 75 retries bounded, 78 does not retry; killing monitor in final image caused one whole-target restart, preserving both groups and Player API OK. Permanent production service was not installed/enabled; transient acceptance units were stopped. -
2026-10-10 interrupted-apply acceptance: real isolated fixtures from SQLite backup/qualified cached rows tested final image. Known prepared config (pending hash
507b2d…) was restored to committed1f9696…before first real sysv restart/start; journal at first start was committed with old IDs [1,15]. Unknown config hash exited 78 with zero activations/restarts and preserved diagnostic state. No qualification evidence was fabricated; no main state was modified. Private report:/home/agent/prepared-acceptance-g2p72yjt/acceptance-report.json; disposable containers cleaned after validation. -
2026-10-10 build/docs/result: Go builder and runtime are digest-pinned;
4824570adds native BuildKit compilation-cache mounts. Built release candidatezapret-autotune-managed-target:rc-4824570, local immutable image IDsha256:011b8e82422a83686322eafddbd4203f9117bf4d9830fa3ec900f0f31538c1ae. Atomically persisted only its selector in private remote.env; image binding, env0600 and SS password preservation verified without printing credentials. New target runs this image, generation29 active[1,15], Player API OK, only queue300; old container PID/start-time unchanged, Xray untouched. README, MANAGED_TARGET and deployment README cover provisioning, actual config forwarding, immutable promotion, service install, backup/restore, failure handling and limitations.go test ./..., affected-race, shell/static checks and native unit syntax passed. No real server reboot or full 90-minute expiry wait was performed; expiry tested with shortened injected budgets. Registry publication, permanent service enablement and final production rollout remain operator decisions; this is a production candidate, not a blanket production-ready claim. -
2026-10-10 transport RCA: captured packet/strace diagnostics only in disposable containers on the target bridge, fixed destination
142.251.153.4. TCP establishment succeeds (~18ms); failed passes retransmit ClientHello without server ACK advancement or first TLS response, not an HTTP-body timeout. Full-snapshot, conflict-checked reassembly of 24 connections showed the old frontend seed passes all 22 non-final-SNI layouts and times out on both final-SNI layouts (one TLS1.2, one TLS1.3; zero bytes after SNI). Rustls extension order changes between requests. This strongly establishes observed strategy layout sensitivity, not a proven Rustls/Lua bug or exact network drop location. An independent heavy-tier review confirmed the conclusion/limits. -
2026-10-10 replacement candidate:
--payload=tls_client_hello --lua-desync=fake:blob=fake_default_tls:tcp_ts=-1000:repeats=1 --lua-desync=multidisorder:pos=1,midsldpassed 24/24 diagnostic connections, including final-SNI in both protocols, then 10 standard checker jobs with 3/3 for TLS1.2 and TLS1.3 (60/60 requests using auto DNS). This is a tested replacement hypothesis, not a universal guarantee. Qualification/evidence rules are unchanged. No working profile/image was switched during this tracing task; target Player API remains OK, old target/Xray unchanged. Temporary trace containers were removed after copying private artifacts; raw captures/reports retained in/home/agent/checker-transport-trace,/home/agent/checker-full-trace,/home/agent/checker-alternative-trace, and/home/agent/alternative-qualification-*.json/.stderr. Next implementation step, if approved: prefer this candidate through the normal managed verify/save/apply pipeline instead of weakening checks or modifying TLS libraries/timeouts. -
2026-10-10 remaining-gates follow-up:
24c29beadds exact GGC scope comparison to healthy monitor probes and authenticated early-timeout rejection for saved candidates (qualification still requires both TLS protocols 3/3).b965842/cb82436correct actual upstream diagnostic metadata and validate DNS IP literals. Medium-tier independent review and actual remote-capture Go checks verified genuine one/two-protocol early timeouts authorize rejection, while a passing report does not; malformed/infrastructure diagnostics remain fail-closed. All local Go tests/build/static checks pass. Deployed final image includescb82436. -
2026-10-10 runtime gates: temporary target-only policy 15s/1/30s demonstrated successful saved frontend recheck/apply without a new frontend tune run and real GGC rotation (
rr17---sn-n8v7kn7d.googlevideo.com↔rr16---sn-n8v7znsz.googlevideo.com) with newly qualified exact-host candidates. A later real saved rejection entered scan/seed fallback: tune run 9 was recorded FAILED when combined revalidation did not pass, and last-good was restored rather than applying insufficient evidence. Thus successful saved-first and safe fallback entry/restoration are verified; a newly applied frontend from that particular fallback attempt is not claimed. Final target generation 25, active IDs [1,13], both groups committed, Player API OK; only NFQUEUE 300 bound. Restored default policy 5m/3/30m; old target remains running and Xray unchanged. -
2026-10-10 full-corpus diagnostic: clean disposable namespace scan tested 8648 TLS1.2 and 4330 TLS1.3 strategies, found 989/935 working respectively, zero scan errors. Diagnostic scan/check chain did not reach check; recovered 1923 intact candidate rows from captured stdout (one row corrupted by interleaved stderr), then independently checked shortlist: 20 passing scenarios, 10 per protocol, each 3/3. Current selector's combined winner passed both protocols 3/3 in two repeats, third repeat had TLS1.2 timeout at 2/3. Raising request timeout from 6s to 20s and fixing a single destination IP did not eliminate sporadic failures; checker Rust client also times out through stable SOCKS. Exact transport cause remains unproven; do not describe timeout as solved or weaken evidence. Safe continuation after validated early failure is implemented; upstream/client-level tracing is the remaining diagnostic work.
-
2026-10-10 worker lifecycle acceptance:
7b332f1cleans only each blockcheck invocation's process group after success/failure, escalates TERM→KILL and checks live membership; target now hasCAP_KILLfor dropped-UID workers. Restored--no-conflict-cleanupto protect foreign processes.23fbf6dadds synchronized orphan/escalation and daemon-preservation regressions;6bacca0preserves private daemon diagnostics. Remote bootstrap qualified and applied frontend candidate 1 and exact-host GGC candidate 2 (rr17---sn-n8v7kn7d.googlevideo.com), committed generation 3, Player API OK. Queues 200–207 are empty; only active queue 300 remains. Recreated final image retains both groups. A controlled target-only daemon stop exposed a separate active-health timeout early-return bug; fixed with delegated, independently verified regressions in8475934. Old target and Xray were not modified. All new commits include Co-authored-by. -
2026-10-10 live recovery retest: deployed final image
8475934, stopped only target-local zapret without changing committed config and waited for normal failure threshold/cooldown. Monitor attempted saved frontend revalidation (no new scan or tune run). Blockcheck returned TLS 1.2 timeout at 1/2, TLS 1.3 3/3; incomplete evidence was correctly rejected, but recovery restoration restarted both last-good groups. Player API returned OK, queues 200–207 were free, and next periodic probe reset consecutive failures to 0; monitor remains alive. Same-IP142.251.156.4curl comparisons through old SOCKS 1080 and new SOCKS 11080 returned HTTP 200 for all 12 requests (3 per TLS 1.2/1.3 per proxy). Worker lifecycle, apply, restoration and periodic monitor are runtime-verified; a fully successful fresh saved-first revalidation remains unproven because blockcheck occasionally times out despite stable proxy requests. Do not weaken 3/3 or describe this as full recovery acceptance. Dedicated target is left running with both committed groups; old container/Xray untouched. -
2026-10-10 remote acceptance: target image built from pinned base and started in a fresh directory/state volume; host SOCKS port
11080was free, old container stayed untouched. Initial managed status confirmed generation0,groups=none, no active candidate IDs, andNFQWS2_ENABLE=0. Automated frontend scan ofyoutube.comcompleted withtotal=4323, working=0; candidate check produced an emptystrategiesarray, recorded one failed run, and bootstrap error caused monitor/entrypoint exit. No strategy was applied. New target remains stopped with its fresh, strategy-free state preserved. This exposed that managed bootstrap should scan the actual Player API host (www.youtube.com) and ordinary no-candidate errors must not terminate ongoing monitoring. Updated code/tests are in progress; rerun required. Old container and Xray were not changed. -
2026-10-10 remote retry: scanning the correct
www.youtube.comhost still producedworking=0. Diagnosis: scan left NFQUEUE workers 200–207 in the isolated target namespace; the subsequentcheck --no-conflict-cleanuppreserved those workers and every candidate immediately failed. A manualcheckafter a standalone scan confirmed the queue-conflict failure. Stopped only the new target (old target/Xray untouched), preserving its empty state. Managed recovery now opts into blockcheck conflict cleanup because it runs only after stopping zapret in the dedicated isolated namespace; ordinary CLI callers retain--no-conflict-cleanup. Local test/build pass; remote rerun pending. -
2026-10-10 retry after worker-cleanup fix: deployed commit
a762763and recreated only the isolated target, retaining generation-0 empty strategy state. Managedwww.youtube.comscan completed; subsequent shortlist check returned an emptystrategiesarray, and the persistent monitor correctly continued into a later recovery scan instead of exiting. At the last reachable check the target was up, generation 0, no candidates, and 3 probe failures; SSH profiledevthen disconnected during the next scan. Acceptance remains incomplete; reconnect and inspect current process/status/report before any further action. Old target and Xray remained untouched. -
2026-10-10 diagnostic follow-up: SSH reconnected. Existing SOCKS
127.0.0.1:1080returned HTTP 200 forhttps://www.youtube.com/; direct host curl and fresh target SOCKS127.0.0.1:11080timed out, as expected with the disabled baseline. Independently ranblockcheckw checkin a clean disposable container on the same target bridge using the existing frontend profile; it passed TLS 1.2 and TLS 1.3, 3/3 each. The default scan corpus omitted this exact profile, whileblockcheckw scan --from-filefound it on the same host in under a second. Repeated strict checks showed intermittent TLS 1.3 timeouts (one protocol 3/3 while the other fell to 1/2); the managed seed now retries the tiny exact-host corpus up to five times before falling back to the hour-long default search. Stopped only the dedicated target to end repeated full scans; its state remains generation 0 with no applied candidates.go test ./..., build, static deploy guard, entrypoint syntax, and diff checks pass. Deploy and remote acceptance rerun pending. Old container/Xray untouched. -
2026-10-10 seed retry follow-up: Repeated checks in one disposable namespace confirmed intermittent TLS 1.3 timeouts persist across attempts. Managed seed was changed to run
blockcheckw checkdirectly (not a scan that leaves NFQUEUE workers), retrying only the small seed; identical TLS 1.2/TLS 1.3 args are now de-duplicated before combined revalidation. The previous five-attempt seed-scan build is stopped; dedicated target state still has no committed candidates. Local tests/build/static checks pass; deploy and runtime verification of the direct-check seed remain pending. Old target/Xray untouched. -
2026-10-10 latest runtime check: Deployed the direct-check seed build. It still fell through to the default full scan; process inspection showed a seed
nfqws2worker holding queue 200 alongside the scan's workers on 201–207. This confirms managed checks leak workers into the target namespace, so retries/default scan can contend on NFQUEUE even though a clean disposable check can pass. Stopped only the managed target; verified it is exited while the old target remains up and the existing SOCKS still returns HTTP 200. Generation remains 0 with no candidates. Next fix must explicitly clean up only blockcheck-owned NFQWS workers before retry/scan checks, then rerun acceptance. Acceptance remains incomplete. -
Added
managed monitorand supervision only in the dedicated target entrypoint: guarded target-owned DB/identity before singleton, policy 5m/3/30m with bounded CLI/env validation, owned-loopback Player API probe/discovery without direct fallback, fixed blockcheck/zapret argv with context cancellation/join. Startup bootstraps only without a qualified active frontend, tries saved scenarios first, then scans; unresolved GGC keeps monitoring; safety/DB errors stop it. SIGTERM waits for monitor restoration before stopping target-local zapret/SS. Local fake CLI/entrypoint tests are present. -
Hardened managed recovery artifacts: общий
revalidateCandidateудаляет старый combined JSON перед каждым check, remove errors/missing/malformed report fail closed; scan shortlist проверяется на regular file и mtime не раньше whole-second scan start (production использует unique temp path). Добавлены fake-only regression tests stale/missing shortlist, stale combined, remove failure и infrastructure classification/restoration. Tests/build/network не запускались; verification deferred orchestrator, CLI/entrypoint не добавлены. -
Добавлен injected
recoverManagedTargetи callback wiring к persisted monitor: frontend bootstrap через scan/check/save/transaction, saved-first qualified IDs (до 10), strict valid non-pass fallback, target-local downtime и bounded restoration, frontend-only rollback boundary перед fresh exact-host GGC revalidation/scan. GGC failure отдельно unresolved, Player API не playback. Immutable candidates/committed IDs сохраняются; cleanup/rollback failure fatal. Fake-only tests добавлены; producer не запускал tests/build/network, verification deferred orchestrator. CLI/entrypoint/live runtime не подключены; старый target и Xray не менялись. -
Добавлены только reusable recovery building blocks:
listQualifiedCandidates(known groups, newest-first, limit 1–10, shared qualification rule) и injected exact-endpoint revalidation сохранённых args. Только полный валидный two-TLS 3-pass nonpass даётerrCandidateNonpass; malformed/incomplete evidence, scope/args mismatch и infrastructure failures fail closed. Definitions/evidence не меняются, fresh GGC остаётся exact-host. Existing proposal recovery использует общий revalidator; managed recovery adapter, monitor CLI/entrypoint и remote calls не добавлены. Focused local-fixture tests добавлены; producer tests/build/network не запускал, verification отложена orchestrator. -
Group-wise managed activation: один или оба qualified frontend/exact-GGC candidate; full desired set (не patch), frontend-only bootstrap до Player API/GGC discovery. Journal v2 сохраняет committed/pending IDs вместе с hash; rollback/crash возвращает прежний список.
managed statusи JSONmanaged active-idsпроверяют IDs/groups через DB и exact rendered hash; missing groups явно unresolved. Legacy v1 сохраняет deployment по exact hash без выдуманных IDs; unknown IDs fail closed для supervisor. Player API OK не означает GGC/video playback или full-profile health. Focused tests обновлены/добавлены; tests/build/network отложены orchestrator. Recovery callback, remote apply, текущий target и Xray не менялись. -
Добавлен internal
runManagedMonitor(ctx, deps): immediate/periodic probe, durable streak/reset, threshold/cooldown recovery через injected callbacks, cooldown от completion при любом результате, fatal DB/lock/finalization errors и cancellable wait. Shared runtime guards выполняются до lifetime nonblockingflockв target-owned directory. Одноразовая startup reconciliation под singleton использует schema-v5 PID/starttime API: exact lease снимается только при доказанном dead/PID-reused owner и запускает crash cooldown; live owner остаётся busy, legacy/unverifiable owner — fail closed. Fake-time unit-тесты scheduler core, reset/cooldown, reopen, concurrent start, cancellation и DB/finalization failures добавлены; tests/build/network не запускались в этом increment — verification отложена orchestrator. Actual recovery adapter/monitor command/entrypoint wiring и развёрнутый live target пока отсутствуют; deploy, контейнер и Xray не затронуты. -
Добавлены
Dockerfile.target, ordered target entrypoint иdeploy/managed-target/compose.yaml: pinned runtime digest, отдельная bridge-сеть,cap_drop: ALLи толькоNET_ADMIN,NET_RAW,SETUID,SETGID(nft/NFQUEUE, raw send и смена UID/GID nfqws2), новый private bind./target-state, отдельный gitignored.env, SOCKS TCP/UDP только на host loopback (default 11080), внутренний health proxy 1080; SS port не опубликован. Startup: ss-server/ss-local → listener → managed init (status при recreation) → zapret2 start; shutdown ограничен target-local процессами/firewall. Только deployment definition и process supervision, не autonomous monitor/recovery. Compose config/tests/build/pull/run/remote producer не выполнял; проверка отложена orchestrator, runtime gates открыты. -
Усилен guarded manual CLI
managed init|status|apply: exact rolemanaged-test, fixed IDzapret-autotune-managed-v1, provisioned runtime marker/base executables и private dedicated mountpoint/var/lib/zapret-autotune/targetобязательны для всех команд.ZAPRET_CONFIGдопускает только/var/lib/zapret-autotune/target/config; standalone full config разрешён только в новом target-owned volume, не поверх существующего service config (include fragments не реализованы). Proxy обязан совпадать сsocks5://127.0.0.1:$SOCKS_PORT; проверяется ownership listening socket процессомss-local. Старый контейнер/произвольный каталог/loopback proxy не проходят guards. Добавлены injected unit-тесты отказов и fresh-target success; transaction engine и shell config safety не изменены. Tests/build/network этого increment отложены producer; контейнер, deploy, remote и Xray не затронуты, image/config-loading compatibility ещё не доказана. -
Добавлена foundation schema v4 и owner identity schema v5: durable policy state по stable service ID, last probe/streak, recovery lock и cooldown. Операции с injected time атомарно записывают probe и захватывают recovery только при threshold/истёкшем cooldown/свободном lock; завершение требует точный ownership token и запускает cooldown от completion time. Stale/duplicate finish не меняет новую lease; crash сохраняет lease до PID/starttime-safe reconciliation под exclusive singleton, с новым crash cooldown. Проверка текущей v5 интеграции отложена orchestrator.
-
Добавлен одноразовый
health youtube: bounded Player API-запрос только через loopback SOCKS (ZAPRET_AUTOTUNE_SOCKS_PROXY, defaultsocks5://127.0.0.1:11080), без ambient proxy/direct fallback. Health требуетplayabilityStatus.status=OK, не streaming URL и не playback. Config валидирует video ID (defaultdQw4w9WgXcQ), interval5m, failure threshold3, cooldown30m.go test ./...,go buildиgit diff --checkпрошли для обоих последних increments. -
Добавлена тестируемая transaction foundation для target-owned config: только квалифицированные stored candidates, separate frontend/exact-GGC profiles, versioned durable journal/backup, atomic replace, injected daemon reload + Player API post-check, rollback и crash reconciliation; external config drift fail-closed. Renderer не сохраняет wildcard GGC scope. На момент foundation CLI ещё не вызывал apply; теперь manual adapter есть, target config/runtime ещё не проверены.
go buildи повторныйgo test ./...прошли для foundation; первый test run поймал прежний flakyTestRunBlockcheckCancellation/killprocess-state race. -
Завершён удалённый ручной GGC scan для
rr16---sn-n8v7znsz.googlevideo.com: TLS 1.2 — 1 525 рабочих стратегий, TLS 1.3 — 800. Shortlist check нашёл 20 проходящих вариантов; точная объединённая стратегия--lua-init=fake_default_tls=tls_mod(fake_default_tls,'rnd') --payload=tls_client_hello --lua-desync=multidisorder:pos=2,midsld:seqovl=1:seqovl_pattern=fake_default_tls --in-range=-s1 --lua-desync=oob:urp=midsldпрошла по 3/3 для TLS 1.2 и TLS 1.3. Результат относится только к указанному hostname; не означает playback/SABR и не применялся. -
Добавлена proposal-only команда
recover googlevideo --video-id ID --proxy socks5://HOST:PORT: discovery одного свежего exact host → qualified schema-v3 сценарии newest-first → combined TLS1.2/1.3 3/3 точных сохранённых args. Первый успешный сценарий сохраняется новым immutable candidate/run и выдаётся как NOT ACTIVE без scan. Только отсутствие eligible candidates или валидные non-pass результаты разрешают обычный scan на уже найденном host; infrastructure/malformed-report ошибки fail closed. Apply/monitor и удалённый scan не затронуты. -
Unit-тесты recovery порядка, fresh-host scope, short-circuit, fallback и fail-closed ошибок прошли; локальные
go test ./...,go buildиgit diff --checkуспешны. -
CLI на Go:
tune youtube,tune googlevideo --video-id ID --proxy socks5://HOST:PORT,recover googlevideo --video-id ID --proxy socks5://HOST:PORT,discover youtube,health youtube,status,history,strategies youtube,render,managed init|status|apply|monitor.check youtubeпока намеренно отказывает; managed activation/monitor только внутри designated target, rollback автоматический; command/entrypoint интегрированы, runtime verification отложена. -
Proposal-only GGC pipeline: Android 21.02.35 discovery через явный proxy → scan TLS1.2/1.3 только одного найденного hostname → data-transfer shortlist (
--take 10 --passes 3) → проверка точной комбинации 3/3 на обоих TLS → один инертный профиль с exact-host фильтром. Ранжирование по blockcheckw, не Selectel. SQLite v3 атомарно сохраняет googlevideo candidate и оба endpoint×TLS evidence; отдельный additive journal сохраняет failed runs.historyиstrategies youtubeпоказывают точный endpoint/group;statusпока относится только к frontend journal. -
Добавлены injectable unit-тесты GGC success/order/scope/filter/persistence, обязательных флагов, discovery failure, неполной/неуспешной combined проверки и fail-closed DB. После исправления exact-host фильтра
go test ./...,go buildиgit diff --checkпрошли локально. Полный новыйtune googlevideoещё не прогонялся удалённо. -
tune youtubeсканирует frontendyoutube.com, проверяет shortlist черезblockcheckwи выдаёт один TLS-профиль только после совместной проверки TLS 1.2 и 1.3 по 3/3. Это предложение конфигурации, оно ничего не применяет. -
SQLite без CGO: миграции до схемы v3, атомарное сохранение успешных/неуспешных tune-запусков, SHA-256 fingerprint нормализованных аргументов,
status, read-onlyhistoryи список предложенных стратегий. v3 добавляет неизменяемые определения кандидатов и evidence по endpoint/protocol без active-состояния; старые предложения не переносятся в кандидаты. База и каталоги создаются с ограниченными правами. -
discover youtube --video-id ID --proxy socks5://HOST:PORTделает запрос к YouTube Android Player API, валидируетserverAbrStreamingUrlи выдаёт только hostname изgooglevideo.com; подписанный URL не выводится. -
Проверки кода после последних изменений: локальные
go test ./...иgo buildпрошли. Docker build проходил после добавления SQLite-зависимости и исправления.dockerignore.
Проверено удалённо
- Read-only инвентаризация Docker-хоста: Docker 29.8.2, kernel 6.8.0-146-generic; используемый zapret2 image
vernette/ss-zapret2:v1.0.2доступен по digestsha256:ba158180f27cd71a291ee521c291490374fd3fcf2f81eb1434ddfb19d35de45b. Текущий target остаётся отдельным и нетронутым. Новую сеть/контейнер ещё не создавали. - В этом image digest доступен
/usr/bin/blockcheckwверсии 0.9.0; это позволяет отдельно проверять его наличие/версию для нового target image, но пока не доказывает route equivalence или безопасную совместную работу scan с активным proxy. - Ранее frontend-комбинация прошла
blockcheckw checkнаyoutube.com: TLS 1.2 — 3/3, TLS 1.3 — 3/3. Ручная проверка YouTube oEmbed через SOCKS также прошла. - Player API-запрос через SOCKS
localhost:1080вернулplayabilityStatus=OKи динамическийgooglevideo.comhostname. - На одном найденном GGC hostname текущая статическая стратегия
fakeddisorder:pos=midsld:tcp_flags_set=SYNпрошла data-transfer check 3/3 для TLS 1.2 и TLS 1.3. Frontend-комбинация на этом GGC hostname не прошла; frontend и GGC требуют отдельных профилей. - Отдельный Selectel speedtest с SNI
googlevideoбыл проверен экспериментально, но не используется для ранжирования: принято решение доверять TLS/data-transfer результатамblockcheckw.
Исторические незавершённые работы (на момент записи)
- Scan и shortlist check завершены, контейнер
zapret-autotune-googlevideo-scanостановился с кодом 0. Проверка exact combined args прошла;tune googlevideoне запускался end-to-end и результаты вручную в SQLite не импортировались. - Новый отдельный
tune googlevideoproposal-only и не меняет frontend-onlytune youtube; удалённый end-to-end запуск команды ещё не выполнен.
Исторические ограничения (на момент записи)
- Проверка реального YouTube video-transfer/SABR. Прямой GET
serverAbrStreamingUrlвозвращаетsabr.malformed_config; hostname discovery иblockcheckwdata-transfer checks не равны проверке воспроизведения видео. - Guarded managed CLI/monitor интегрированы внутри designated target: transaction core, bootstrap/recovery callback и deployment definition есть, но нет proven image/runtime compatibility, выполненного container provisioning и реально запущенного managed target. Одноразовый Player API health сам не запускает live automation. Цель: новый отдельный prod-like zapret2-ss контейнер только в тестовой среде; существующий контейнер не трогать. Стабильный настраиваемый loopback SOCKS для Xray; Xray config вне scope. Перед runtime пройти route/rollback gates.
- Полный сервис из требований: YAML-конфигурация сервисов, endpoint-история/покрытие, daemon/периодический мониторинг, API/метрики и multi-service режим.
Исторические следующие шаги (текущие gates указаны выше)
- Проверить новый
tune googlevideoиrecover googlevideoend-to-end на удалённом сервере; отдельно решить, как импортировать или переиспользовать уже полученные scan результаты без повторного перебора. - Воспроизводимое описание отдельного prod-like target добавлено в
deploy/managed-target; orchestrator должен проверить Compose syntax. Build/run отложены. До запуска проверить baseline-конфиг и NFQUEUE внутри container network namespace; текущие mounts, сеть, порты и конфиг не переиспользовать. - Проверить готовый manual managed CLI на новом изолированном target; подтвердить shell config rendering, config binding, full firewall/daemon restart и pre/post health.
- Проверить bootstrap/recovery callback и новую CLI/entrypoint интеграцию focused tests/build. Startup singleton reconciliation уже есть; live runtime ещё не проверен. До deployment проверить shutdown grace: bounded rollback/restoration может потребовать больше текущих 45s; Docker definition в этом increment не менялась.
- До autonomous mode доказать safety gates из
Architecture.md: изоляцию target, эквивалентность managed SOCKS пути, версионирование, atomic activation/rollback и crash recovery. - Отдельно определить реальную video/SABR-проверку и traffic budget; API health не равен playback и не обнаруживает все GGC playback failures.