What update scope setting prevents duplicate writes during PyCharm Live Edit retries?

PyCharm's Live Edit feature synchronizes CSS, HTML, and JavaScript changes to the browser in real time, aiming to eliminate full application restarts. A design concern emerges when retried updates interact with front-end code that expects idempotent write behavior, such as component state initialization or DOM mutation guards.

The feature's update scope and timeout configurations influence which changes are re-sent, but their interaction with write-idempotency mechanisms is not explicitly documented. This creates uncertainty about whether retried updates may trigger duplicate asset writes or violate expected side-effect boundaries in frameworks like React or Vue.

Which Live Edit update scope mode minimizes the risk of duplicate front-end writes? Can the retry mechanism be constrained to avoid re-applying changes to already-stable DOM segments? What criteria does Live Edit use to distinguish a new change from a retried update?