docs: record clean RC bootstrap and lifecycle acceptance

Co-authored-by: GPT-6 <gpt-6@openai.com>
This commit is contained in:
ZeusinaandGPT-6 Bot committed 2026-10-11 10:59:25 +03:00
1 parent 11f9197ba8
commit 8826c591dc
4 files changed
+76 -28

No files matched your search

+13 -9
View File
@@ -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;