# zapret2-autotune Go CLI for scanning and checking YouTube TLS bypass strategies with `blockcheckw`. Build the Docker image with: ```sh docker build -t zapret-autotune . ``` The `tune youtube` command scans and checks candidate strategies; it prints a proposed `NFQWS2_OPT` and does not apply configuration or restart services. Tune runs are recorded in pure-Go SQLite (no CGO). A verified combined candidate and its TLS1.2/TLS1.3 3/3 pass results are committed together before options are printed; failed scans/checks are recorded as failed runs without a candidate. Database initialization or persistence errors return nonzero and emit no options. `status` shows the latest recorded run, or explicitly says there is no recorded run. Candidates are **PROPOSED, not active**; there is no apply command and production health is not checked. A later failed run is shown instead of an older proposal. An output-write failure can leave a verified proposal recorded, but still returns nonzero. Set `ZAPRET_AUTOTUNE_DB` to override the default database path `/var/lib/zapret-autotune/autotune.db`. The parent directory is created if needed; it must be writable. In Docker, mount that directory to retain history: ```sh docker run --rm -v autotune-data:/var/lib/zapret-autotune zapret-autotune status ``` Schema version 2 is initialized transactionally on `tune` and `status`; subsequent opens are idempotent and newer, unsupported schema versions are rejected. Proposed runs store a SHA-256 fingerprint of validated arguments with separator whitespace normalized and argument order preserved; repeated proposals retain separate history rows. Failed runs have no fingerprint. Version 1 history is upgraded atomically, rejecting invalid proposed arguments without changing it.