docs: record clean RC bootstrap and lifecycle acceptance
Co-authored-by: GPT-6 <gpt-6@openai.com>
This commit is contained in:
1 parent
11f9197ba8
commit
8826c591dc
4 files changed
+76
-28
No files matched your search
+16
-11
@@ -135,7 +135,7 @@ identity/SOCKS guards. Fake-only checks are added, but tests/build are deferred
|
||||
to the orchestrator. `managed monitor` now binds those callbacks and only the
|
||||
dedicated target entrypoint starts it; no live/runtime validation has occurred.
|
||||
|
||||
## Dedicated monitor integration (live acceptance pending)
|
||||
## Dedicated monitor integration (isolated clean-run acceptance passed)
|
||||
|
||||
`zapret-autotune managed monitor [--interval 5m] [--failure-threshold 3]
|
||||
[--cooldown 30m]` uses the health environment defaults. Interval is positive and
|
||||
@@ -166,13 +166,16 @@ all three children; unexpected monitor exit is not a successful shutdown.
|
||||
SIGTERM/SIGINT cancels and waits the monitor before target-local zapret stop and
|
||||
SS child termination/wait. Existing targets and Xray remain unchanged. Deployment
|
||||
allows 240s Compose shutdown grace for bounded
|
||||
monitor cancellation/restoration and child joins. Code integration is not
|
||||
image/routing/signal live verification.
|
||||
monitor cancellation/restoration and child joins. Clean RC `d8316e6` has passed
|
||||
isolated image/routing, bootstrap, periodic probe, monitor-crash cleanup, graceful
|
||||
stop and persistent recreation gates; see the
|
||||
[recorded source/image and PASS report](deploy/managed-target/README.md#recorded-clean-run-acceptance-2026-10-11-pass).
|
||||
This does not establish playback or blanket production approval.
|
||||
|
||||
Injected unit tests cover exact identity/path/config, mountpoint refusal,
|
||||
old-container-like env, SOCKS port/process refusal, correct fresh-target success,
|
||||
non-overwrite, transaction rollback and redaction. Tests/build/network are
|
||||
deferred to the orchestrator; not run by this increment:
|
||||
non-overwrite, transaction rollback and redaction. Verification results are
|
||||
recorded in [PROGRESS.md](PROGRESS.md). Focused local checks can be rerun with:
|
||||
|
||||
```sh
|
||||
go test ./cmd/zapret-autotune -run TestManaged
|
||||
@@ -360,9 +363,11 @@ restore a known consistent backup. Only then manually start the target with Comp
|
||||
There is no automatic wipe or
|
||||
automatic adoption path.
|
||||
|
||||
Rollout acceptance remains pending real isolated-target restart/deadline tests:
|
||||
empty bootstrap, saved-first recovery, exact-host GGC rotation, image binding,
|
||||
NFQUEUE activation/rollback, SIGTERM during downtime, deadline restoration,
|
||||
in-container retry limits/backoff, durable two-hour absence wait and resumption, persistent
|
||||
recreation and backup restore. Perform these on the new target only; local unit
|
||||
or static checks cannot establish production readiness.
|
||||
The recorded clean RC PASS covers empty-state bootstrap through qualified frontend
|
||||
and exact-host GGC apply, image/config binding, ongoing probes, in-container monitor
|
||||
crash restart, graceful stop and persistent recreation. Earlier recovery, rollback,
|
||||
rotation, retry and absence fixtures are distinguished in [PROGRESS.md](PROGRESS.md);
|
||||
do not attribute all of them to the clean run. No media playback, real 90-minute
|
||||
watchdog expiry or real two-hour absence expiry wait is claimed. Production rollout
|
||||
and backup-restore acceptance remain operator gates on a new isolated target;
|
||||
local unit/static checks and isolated PASS do not establish blanket production readiness.
|
||||
@@ -4,6 +4,10 @@
|
||||
|
||||
## Текущий статус
|
||||
|
||||
- **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.
|
||||
- **Scope/limits:** both older targets' images, container IDs, PIDs, start times and ports stayed unchanged (existing managed PID518298, old SS PID266922); no host-manager or Xray changes. Private final PASS report: `/home/agent/zapret2-managed-clean-d8316e6-45bb14ba/final-cleanrun-report.json`, raw artifacts in `final-evidence/`. This is isolated clean-run acceptance, not blanket production approval, a playback test, or a real 90-minute watchdog wait. The full 90-minute wall-clock expiry was not waited out; deadline behavior remains covered by shortened/injected tests. The working-target entry below describes the unchanged existing target, not the additional clean RC.
|
||||
- **2026-10-11 container-owned control, committed/deployed:** `5258ae2`, `6467108`, `fe23eec` replace external supervision with PID1-owned runtime-cycle retries (three starts per rolling six hours, cancellable 15s/30s backoff capped at 60s). Guard/config/DB/rollback/cleanup failures remain fail-closed. Reconciliation precedes activation; fresh-shell watchdogs avoid EXIT/TERM trap deadlock; private monitor sessions allow cleanup of orphaned scan workers before restart. SS uses private JSON, never exported password/argv. Graceful SIGTERM joins/restores before stopping owned daemons; Compose has no restart policy and 240s grace, monitor join 45s. Host/container-platform lifecycle belongs to the operator, not a generated host manager. Historical transient acceptance units were unloaded and the tracked systemd unit removed.
|
||||
- **2026-10-11 strategy absence:** genuine validated no-qualified-strategy results persist `max(2h, configured cooldown)` in SQLite, preserve longer existing deadlines and other leases, and survive monitor/container startup. Lightweight probes continue; heavy saved-first/scan/apply waits until expiry. Other ordinary outcomes retain 30m cooldown. Malformed reports and explicit nfqws2 infrastructure failures are vetoed before both positive and negative selection; they are never disguised as absence. Qualification remains both TLS protocols 3/3. The separate 90-minute whole-job watchdog plus bounded restoration remains abnormal, not normal absence.
|
||||
- **Verification:** full Go suite, targeted race tests and shell/static/Python fixtures pass. Negative-only checker fault injection demonstrated a persisted 7200-second pause, unchanged checker count 7→7 through internal monitor restart, same container/PID1, DockerRestartCount0, zero candidates and graceful exit0. Active-check crash fixture demonstrated old separate-PGID workers gone before replacement activation, unowned session peer preserved, direct unchanged PID1/container and exit0. Private reports: `/home/agent/container-absence-acceptance-roqcpxq1/actualreport.json`, `/home/agent/active-scan-crash-5z2a6xb_/actual-report.json`. These validate control flow, not new network qualification; real two-hour wall-clock expiry was not waited out (expiry covered by injected-clock tests). Numeric PID signalling retains the usual read/signal PID-reuse race; strict reuse-proof signalling would require pidfds.
|
||||
|
||||
@@ -2,15 +2,19 @@
|
||||
|
||||
Go CLI for scanning and checking YouTube TLS bypass strategies with `blockcheckw`.
|
||||
|
||||
## Production preparation (acceptance pending)
|
||||
## Production preparation (isolated clean-run acceptance passed)
|
||||
|
||||
The standalone deployment candidate is a **new isolated target**, never an
|
||||
upgrade/adoption of an existing zapret or Xray service. The legacy `managed-test`
|
||||
role and fixed identity guards remain intentional, including for prod-like runs.
|
||||
See [release, configuration, upgrade and rollback guidance](MANAGED_TARGET.md#production-preparation)
|
||||
and the [container deployment instructions](deploy/managed-target/README.md).
|
||||
Pinned builds and supervision are preparation, not production acceptance: real
|
||||
restart/deadline tests and end-to-end target validation remain rollout gates.
|
||||
The clean RC `d8316e6` passed isolated bootstrap, qualification, ongoing probes,
|
||||
monitor-crash cleanup, graceful stop and persistent recreation on loopback SOCKS
|
||||
`11081`; the existing target on `11080` remains untouched. See the deployment
|
||||
guide for the exact source/image and private PASS report. This is not blanket
|
||||
production approval or playback verification; no real 90-minute expiry wait was
|
||||
performed. Each production rollout still needs its own validation.
|
||||
Select an immutable managed-target digest with `ZAPRET_AUTOTUNE_IMAGE` in the
|
||||
private deployment `.env`; tags/local defaults are only build/test candidates.
|
||||
Bootstrap/recovery shares a 90-minute whole-job deadline plus a separate 30-second
|
||||
@@ -30,7 +34,7 @@ recovery preserve a configured recovery cooldown longer than two hours.
|
||||
This is not a watchdog timeout:
|
||||
ordinary recovery cooldown stays 30m, and the abnormal whole-job ceiling stays 90m.
|
||||
|
||||
## Manual managed-test activation (not deployed)
|
||||
## Manual managed-test activation
|
||||
|
||||
`managed init|reconcile|status|active-ids|apply` requires exact role `managed-test`, target ID
|
||||
`zapret-autotune-managed-v1`, a provisioned runtime marker and zapret executables,
|
||||
@@ -48,14 +52,14 @@ group, fixed target init executable and explicit runtime-config
|
||||
binding. It uses full target-local firewall/daemon restart and Player API post-check, with
|
||||
atomic rollback on failure. See [MANAGED_TARGET.md](MANAGED_TARGET.md) for guards
|
||||
and provisioning prerequisites. An isolated pinned deployment definition is in
|
||||
[deploy/managed-target](deploy/managed-target/README.md); acceptance remains pending.
|
||||
[deploy/managed-target](deploy/managed-target/README.md), including recorded clean-run PASS.
|
||||
An injected bootstrap/saved-first recovery adapter now connects the persisted
|
||||
monitor foundation to blockcheck, immutable candidates and transactional apply.
|
||||
`managed monitor` and the dedicated target entrypoint now wire these adapters;
|
||||
this increment is not tested by the producer or live/runtime verified.
|
||||
No remote activation or Xray changes are included. Image
|
||||
compatibility and route/rollback gates are not yet remotely proven; adapter
|
||||
tests/build are deferred to the orchestrator.
|
||||
the isolated target has been remotely activated and runtime-verified as recorded
|
||||
in [PROGRESS.md](PROGRESS.md). Existing targets and Xray remain unchanged.
|
||||
Clean-run PASS does not imply every recovery/fault gate was exercised in that run;
|
||||
the progress log distinguishes earlier tests and remaining production limits.
|
||||
|
||||
The apply flags are the entire desired group set, not a merge: a single-group
|
||||
apply removes the other group. Frontend-only supports bootstrap discovery;
|
||||
|
||||
@@ -104,11 +104,46 @@ only after safe cleanup. Monitor health is YouTube Player API status through the
|
||||
not video playback/SABR; GGC candidates are scoped to the exact discovered
|
||||
hostname.
|
||||
|
||||
The deployment has not yet passed live runtime acceptance. Validate the pinned
|
||||
image's JSON config loading, Lua/fakes, `ZAPRET_CONFIG` binding, target-local
|
||||
routing, NFQUEUE activation/rollback, signal cleanup and persistent recreation
|
||||
on this new target only. Do not widen capabilities or reuse existing config or
|
||||
network as a workaround. Verify the complete unattended path: empty profile →
|
||||
frontend/API candidate scan and apply → exact-host GGC candidate scan and apply
|
||||
→ ongoing probes → saved-first recovery, falling back to scan only when saved
|
||||
scenarios validly fail.
|
||||
## Recorded clean-run acceptance (2026-10-11): PASS
|
||||
|
||||
Tested source RC: `d8316e695bc36e1243c111e19bb1e527355907b6`; local tag
|
||||
`zapret-autotune-managed-target:rc-d8316e6`; immutable image
|
||||
`sha256:5636aa9031fd0f6a0513f2e22cc0c39b1c806e9714b7f9ac040c8713d6a26c6c`.
|
||||
The image was built from that source git archive with pinned inputs, not from
|
||||
the later documentation commit. Private source root:
|
||||
`/home/agent/zapret2-autotune-rc-d8316e6`.
|
||||
|
||||
The additional clean Compose project `zapret-autotune-clean-d8316e6-45bb14ba`
|
||||
uses root `/home/agent/zapret2-managed-clean-d8316e6-45bb14ba` and host SOCKS
|
||||
TCP/UDP `127.0.0.1:11081`. It is left running for inspection; the existing
|
||||
managed target on `11080` and older SS target remain untouched.
|
||||
|
||||
- Before launch, state was empty, root-owned and mode `0700`; the independent
|
||||
secret was 64 hex characters and `.env` mode `0600`. Real `blockcheckw` was
|
||||
used, without mocks or copied config/candidates. Fresh init was observed;
|
||||
fast bootstrap meant no exact generation-0 status snapshot was captured.
|
||||
- Bootstrap committed generation2, frontend ID1 (verified layout-safe fake +
|
||||
multidisorder seed) and exact-host GGC ID2 for
|
||||
`rr17---sn-n8v7kn7d.googlevideo.com`. Both have valid raw TLS1.2/TLS1.3
|
||||
evidence, 3/3 each. Periodic `lastProbeAt` advanced, counter0, recovery idle.
|
||||
- Monitor SIGKILL changed host PID522765→525271 in the same container/PID1,
|
||||
DockerRestartCount0, preserving IDs[1,2] and config hash
|
||||
`57e639c98420be73a8ec4754b20ba975d81aced44215ed547b1ac029c89c14de`.
|
||||
Graceful stop exited0 in 0.61s with no worker leaks. Forced recreation
|
||||
(`5af686e2ad94…`, host PID525625) retained generation2, IDs and hash.
|
||||
- Post-recreation counters1 then2 were observed; their cause is unproven.
|
||||
A fresh-discovery GGC mismatch sample is not proof of the actual error cause.
|
||||
The next default probe at 07:54 reset the counter to0, no active recovery.
|
||||
Player API was OK and host SOCKS curl to `www.youtube.com` returned HTTP200.
|
||||
- Both older targets' images, IDs, PIDs, start times and ports were unchanged
|
||||
(managed PID518298, old SS PID266922); no host-manager or Xray changes.
|
||||
|
||||
Private PASS report: `final-cleanrun-report.json` under the clean root above;
|
||||
raw artifacts: `final-evidence/`. This is isolated clean-run acceptance, not
|
||||
blanket production approval or media playback/SABR verification. No real
|
||||
90-minute watchdog wait was performed; shortened/injected tests cover expiry.
|
||||
Saved-first recovery, rollback and other fault-injection results are recorded
|
||||
separately in [PROGRESS.md](../../PROGRESS.md), not implied by this clean run.
|
||||
For any new rollout, validate its own image binding, routing and lifecycle gates
|
||||
on the new target only; never widen capabilities or reuse existing config/network
|
||||
as a workaround.
|
||||
Reference in new issue
Block a user