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

+16 -11
View File
@@ -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.