feat(storage): persist verified strategy scenarios
Co-authored-by: GPT-6 <gpt-6@openai.com>
This commit is contained in:
1 parent
cf79e89efd
commit
7fad9b3b5c
7 files changed
+466
-12
No files matched your search
@@ -50,8 +50,18 @@ it must be writable. In Docker, mount that directory to retain history:
|
||||
docker run --rm -v autotune-data:/var/lib/zapret-autotune zapret-autotune status
|
||||
```
|
||||
|
||||
Schema version 2 is initialized transactionally on `tune` and `status`; subsequent
|
||||
Schema version 3 is initialized transactionally on `tune` and `status`; subsequent
|
||||
opens are idempotent and newer, unsupported schema versions are rejected.
|
||||
|
||||
Schema v3 adds immutable strategy candidate definitions (group, declared exact
|
||||
endpoints, args and normalized-args fingerprint) and endpoint/protocol evidence.
|
||||
Each newly successful tune saves its exact verified combined frontend profile for
|
||||
`youtube.com`, both TLS measurements, raw measurement JSON and checked timestamps
|
||||
in the same transaction as the existing run. Qualification requires every declared
|
||||
endpoint to pass exactly 3/3 for both TLS1.2 and TLS1.3, with full success/coverage.
|
||||
Existing v2 history is unchanged and is not backfilled into independent candidates.
|
||||
Candidates have no active/installed state; apply, monitor and GGC integration remain
|
||||
unimplemented.
|
||||
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
|
||||
|
||||
Reference in new issue
Block a user