An immediate write cancels a node's pending debounced content write #3036

Overview

An immediate-mode write for a node cancels that node's still-debounced write, and the cancelled write's changes are never sent. The typical trigger is typing in a task and then, within the debounce window (~500 ms), changing a typed field such as clicking its checkbox or changing its status. The typed write goes out; the typed text is dropped. The UI still shows the text, so nothing looks wrong until the node is reloaded.

Details

• SimplePersistenceCoordinator.persist() calls cancelPending(nodeId, …) when a new write for a node arrives while none is executing. This cancels a pending debounced operation regardless of its kind.
• A generic updateNode() content write captures only the fields it changed, so the write that cancelled it does not carry the content.
• Typed writes are protected against the reverse case: staged typed fields are flushed by whichever write for the node runs next. Generic debounced writes have no such protection.

Acceptance Criteria

• A debounced content write that is cancelled by an immediate write for the same node still reaches the server, either sent by the cancelling write or flushed ahead of it
• Regression test: type in a task, then change its status before the debounce fires; after both settle, the server holds both changes

Related

• Found in the review of Type person and project nodes like task (closes #2807) #3033 (typed person/project nodes)