From c78b51d341ff2e3ba17a450cbcb6a9af74a74356 Mon Sep 17 00:00:00 2001 From: Anatolii Hrynchuk Date: Mon, 2 Nov 2026 11:57:19 +0200 Subject: [PATCH] Record completed v0.6.30 release validation --- Release/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Release/README.md b/Release/README.md index b29dcd5..75f8ef3 100644 --- a/Release/README.md +++ b/Release/README.md @@ -9,7 +9,7 @@ - The guarded retry and failed-paste readback handling require **Write log**, which enables manual-conversion readback. Clipboard restoration remains conditional on ownership. ## Validation -During development, conversion integration passed for permanently blocked paste, unexpected editor content, clearing fictional previous results, ignored-first-paste recovery, clipboard restoration, repeat conversion and partial-selection recovery. Final desktop reruns were interrupted by concurrent keyboard input into the test editor and are not claimed as passing. 48 updater regression checks passed. Release executable versions and manifest hashes are verified before publication. The complete unrelated desktop-interaction suite was not rerun for this focused fix. +The final isolated conversion integration run passed: permanently blocked paste, unexpected editor content, clearing fictional previous results, ignored-first-paste recovery, clipboard restoration, repeat conversion and partial-selection recovery. Typo integration also passed, including Undo and uninterrupted typing. 541 input/UI checks (240 DPI), 105 sync/protocol checks, 483 native regressions and 48 updater checks passed. All release executable versions and manifest hashes were verified. Earlier interactive attempts were interrupted by concurrent input or a transient clipboard-restoration assertion; the final isolated rerun passed. ## Limitations The cause of every ignored paste is not established. This release does not claim to solve all asynchronous selection failures in ChatGPT/browser editors. Keep Write log enabled and send complete operation details if the issue recurs. Native retry is bounded to one attempt; it is not a general retry policy for other applications. All existing dictionary-correction and synchronization limitations remain.