docs: record saved-first rotation and full-scan acceptance
Co-authored-by: GPT-6 <gpt-6@openai.com>
This commit is contained in:
1 parent
dd98398e77
commit
195490af85
1 file changed
+4
@@ -4,6 +4,10 @@
|
|||||||
|
|
||||||
## Готово
|
## Готово
|
||||||
|
|
||||||
|
- **2026-10-10 remaining-gates follow-up:** `24c29be` adds 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`/`cb82436` correct 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 includes `cb82436`.
|
||||||
|
- **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:** `7b332f1` cleans only each blockcheck invocation's process group after success/failure, escalates TERM→KILL and checks live membership; target now has `CAP_KILL` for dropped-UID workers. Restored `--no-conflict-cleanup` to protect foreign processes. `23fbf6d` adds synchronized orphan/escalation and daemon-preservation regressions; `6bacca0` preserves 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 in `8475934`. Old target and Xray were not modified. All new commits include Co-authored-by.
|
- **2026-10-10 worker lifecycle acceptance:** `7b332f1` cleans only each blockcheck invocation's process group after success/failure, escalates TERM→KILL and checks live membership; target now has `CAP_KILL` for dropped-UID workers. Restored `--no-conflict-cleanup` to protect foreign processes. `23fbf6d` adds synchronized orphan/escalation and daemon-preservation regressions; `6bacca0` preserves 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 in `8475934`. 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-IP `142.251.156.4` curl 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 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-IP `142.251.156.4` curl 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.
|
||||||
|
|
||||||
|
|||||||
Reference in new issue
Block a user