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

+43 -8
View File
@@ -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.