Release v0.2.3: fix Settings overlap and repeated-conversion logging

README.md

@@ -112,7 +112,7 @@ only bounded previews/metadata stay in memory. Image data is loaded on demand an
 the history popup is hidden. Settings **Write log** (`writeLog`, enabled by default) controls all
 log writes. Disabling it also clears diagnostic context from memory; existing log files remain.
 Successful operations stay in a memory buffer of at most 40 diagnostic events for 30 seconds.
-Only failures or suspected repeated commands flush this context to `kswitcher.log`; flushed
+Only failures flush this context to `kswitcher.log`; flushed
 context is discarded. Ordinary application errors are also logged when logging is enabled.
 Incident context contains tracked physical input, the expected word, copied text, conversion result,
 and layout IDs, correlated by request ID even when verification fails. Text fields use quoted,
@@ -121,8 +121,8 @@ original length and a truncation flag; each field is limited to 512 UTF-16 code
 Manual conversion attempts in `kswitcher.log` have request IDs and explicit outcomes, including
 busy, empty copy, verification mismatch, unchanged conversion, and cancelled paste. Requests
 record the process, window, input version, and repeated attempts within ten seconds without new
-input. A second repeated manual command triggers a suspicion, not proof of failure; intentional
-layout cycling can also trigger it. An unchanged result containing no letters, or a direct command
+input. Successful repeated commands do not flush the log; intentional layout cycling is normal.
+An unchanged result containing no letters, or a direct command
 to the detected current layout, is treated as expected. `paste-sent-unverified` means Windows
 accepted the paste shortcut; it does not prove that the editor applied the replacement.
 The previous 256 KiB log is retained as `kswitcher.log.1` when the current log rotates.