Repository navigation
Fix Trim, retained saves, indicators and chrome history routing - #7
Merged
Merged
Conversation
Preserve guarded Undo/Redo and pending input through native lifecycle boundaries. Source and tests only; qualification evidence remains in the local verification branch. Releases remain held.
AlexMikhalev
marked this pull request as ready for review
October 18, 2026 13:00
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Four observed editor failures are addressed in this draft:
Native receipt, epoch, CAS, draft and history guards are unchanged.
The new history regression uses the real Rust document: it commits Concern, returns focus through Escape, checks whole-alternative Undo/Redo, verifies actual synonym removal/restoration, and compares saved source/history. The unchanged test fails before the fix (
chrome Ctrl+Z was not consumed) and passes afterward in installed Chrome and Firefox. It also checks keyboard containment, editable/outside targets, composition and teardown. These are browser integration results; the new package's native Windsurf qualification is still pending. A broader local 13-case transcript passed its assertions but its outer cleanup failed, so that invocation is retained as failed rather than admitted as a clean run.Release admission also requires real hosted macOS Chrome and Firefox copy/paste against one transferred CI archive, with actual saved files, trusted plain/HTML input, normalized newlines, caret and rich-node checks. Both families must pass. The publisher independently rejects stale, mismatched or failed proof before calling any publishing API. The portable unit contract preserves typing/newline assertions and separately tests empty untrusted ClipboardEvents; it does not substitute synthetic input for this OS gate.
Current validation:
8b4bbf59b4aefedd39d7c7c0053e4ff50525ddfc: workspace CI is in progress; publication contract passes. No new CI package or full-suite pass is claimed yet.Remaining gates include the new CI-derived package's native save/reopen, synonym registration and all 41 Windsurf checks. Installed Firefox153's original full headless audit retains two focus failures; controlled probes do not yet establish a fix. A separate interactive diagnostic retains its own failures and is not used as a waiver. Other native hosts and final immutable marketplace-package installation admission remain incomplete.
Draft source review only. All releases remain held. No merge, tag, marketplace publication or Zed application-fork change is included.