feat(recovery): retry saved Googlevideo scenarios first

Co-authored-by: GPT-6 <gpt-6@openai.com>
This commit is contained in:
ZeusinaandGPT-6 Bot committed 2026-10-09 23:10:25 +03:00
1 parent 6220eb0b31
commit aaa8f751c6
7 files changed
+345 -7

No files matched your search

+20 -2
View File
@@ -34,8 +34,26 @@ their existing target constraint. Database failures emit no options.
Signed URLs are not printed. Scanner diagnostics are retained in restricted
artifact files rather than relayed to the terminal. No configuration is applied,
no profile is marked active, and no service is restarted. The staged pipeline is
scan/propose now → eventual install → monitoring/recovery; the latter stages are
**not implemented**. No-argument `tune youtube` remains frontend-only and unchanged.
scan/propose now → eventual install → monitoring; install and monitoring are
**not implemented**. Manual proposal-only recovery is available below.
No-argument `tune youtube` remains frontend-only and unchanged.
## Alternatives-first recovery (proposal only)
```sh
zapret-autotune recover googlevideo --video-id dQw4w9WgXcQ --proxy socks5://localhost:1080
```
Recovery discovers the current exact cache host once, then rechecks qualified
schema-v3 `googlevideo` candidates newest-first using their exact saved arguments.
Qualification covers every saved endpoint × TLS protocol; revalidation checks
the fresh host for combined TLS1.2+TLS1.3 3/3. The first passing scenario is saved
as a new immutable candidate/run scoped to that host and emitted as an exact-host
proposal, **not active**. No scan runs after a passing saved scenario.
Only no eligible candidates or complete, valid non-passing evidence permit the
normal tune scan on the already-discovered host. Database, discovery, cancellation,
runner and malformed/incomplete-report errors fail closed without a fallback scan.
This command does not apply configuration, restart services or start monitoring.
## Cache-host discovery