v1.3.55 - Explicit draft conflict recovery

I added explicit recovery choices for conflicting drafts: compare retained or current editor text against a fresh saved-record snapshot without replacing either, then explicitly retain a separate scoped copy. Pending choices are revalidated against input, revisions, account/document/lifetime and expiry at the locked effect.

The dependency-free synthetic browser lab uses bounded copy retention with no automatic eviction, overwrite, merge or unknown-write replay. Copy acknowledgements do not mark editor text saved. The prior save-receipt protection remains intact, and portable guidance describes these decision and evidence boundaries.

Validation includes 53 focused conflict/recovery tests, 964 source tests, 964 exact-package tests in the disclosed local serial-file mode, eight disposable upgrade combinations and 37 task-owned browser DOM/native-store checkpoints. Substantive non-author review accepted the exact proposal. All required PR, push, main and tag installer checks and CodeQL coverage passed, with 42 successful job execution logs and zero open alerts. One zero-step hosted runner-acquisition cancellation was preserved and its single authorized targeted retry passed; carried job IDs were not counted as new executions. Linux retains three existing skips per hosted suite.

Earlier local default-mode package timeouts remain preserved and unexplained. These observations establish no real authentication/service, secure storage, crash/restart durability, distributed exactly-once guarantee or original-app parity. File verification does not establish that an existing host session reloaded instructions.