docs(review round 18): scenario A = L1 memory hit is expected (not a failure), tmp_guard liveness works in docker mode via pid-namespace + heartbeat, dashboard honesty note (4/28 panels remapped to 0.5.3 metrics, Coordinator stays empty)
wiki: review round-6 -- TTFT-UP->DOWN typo fixed, Retrieved->L2-read evidence wording, Restart-accounting NEEDS TESTING, Recipes-Integration verify-engine gate
wiki: evidence-criteria wording aligned with actual test-recovery pattern (not just Retrieved)
wiki: strict recovery protocol v2 + one-command identity setup + pinned lmcache install - Quick-Start (x3): identity now filled AND verified by scripts/setup-identity.sh (all mandatory fields, no manual paste); lmcache installed from pinned requirements-lmcache.txt - Persistence-and-Recovery (x3): strict acceptance protocol -- log-position markers, store-before-restart, L2-vs-L1 evidence distinction, hard-fail readiness, machine PASS/FAIL verdict
wiki: full documentation in EN/RU/ZH (10 pages x3) Home, Quick-Start, Architecture, Configuration, Persistence-and-Recovery, Storage-and-Eviction, Recipes-Integration, Security, Troubleshooting, FAQ. All commands as-is (no placeholders), all links verified internally. Recipes integration (KV_PERSIST=1) documented in all three languages.