Skip to content

v1.3.54 - Add browser draft recovery trial

Choose a tag to compare

View all tags
@ShadowSwaps ShadowSwaps released this 28 Oct 22:23
v1.3.54
0ff0c2f
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

I added a separate, dependency-free browser lab and focused companion guidance for reload and draft recovery.

  • Saved records, checkpointed drafts and editor memory remain distinct. Restore is explicit and remains unsaved.
  • Cooperative locked writes protect changed draft slots and newer saved revisions. Recovery is bound to visibly simulated account, document and lifetime scopes.
  • Real browser observations cover reload and tab close/reopen, controlled failed/interrupted saves, newer-edit protection, identity changes, malformed/stale/future storage and acknowledgement-loss readback.

Independent review identified an older save receipt that could incorrectly mark newer unsaved text clean. I corrected sequence applicability and saved-base reconciliation, preserving newer dirty text and checkpointing it through the existing slot comparison. The rejected proposal and original probe failure remain in the review history.

Validation includes 28 focused tests, 939/939 source and exact extracted-package tests, eight disposable upgrade combinations, 52 candidate browser checkpoints and 20 checkpoints on four faulty copies that passed ordinary controls before named mismatches. A controlled acknowledgement hold after a real native storage write exercises the corrected boundary; it does not establish an uninstrumented browser schedule. Required hosted CI/CodeQL and substantive independent storage/recovery review are recorded with the exact released tree and archive.

Installer/updater, integration and CI code remain unchanged. The historical macOS crypto-harness timeout remains cause-unknown; no new diagnostic comparison or retry is part of this trial. Linux retains three existing hosted-suite skips. These finite same-author browser observations use synthetic identity/data and establish no real authentication/service enforcement, native storage-denial coverage, browser-process restart/crash durability, original parity or model quality. File verification does not prove host instruction reload.

Assets 4
Loading