Repository navigation
fix(editor): preserve saves and incomplete AI responses - #281
Merged
Merged
Conversation
Deploying document with
|
| Latest commit: |
052cead
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://e252368c.document-7hm.pages.dev |
| Branch Preview URL: | https://codex-save-integrity-and-bro.document-7hm.pages.dev |
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.
Exports could return bytes from a replacement document, failed opens could publish unmounted metadata, and incomplete AI output could advance tools or queued work. Bind these operations to their owners, retain incomplete output safely, and validate the resulting behavior through service-worker-controlled browser fixtures and balanced CI shards.
Merge Verdict
[APPROVE]
Independent reviews covered save/open ownership, AI completion/context, and browser/CI behavior. All actionable findings were fixed with regressions and focused re-review.
Summary
Risk Analysis
Design Decisions
libevent-2.1.so.7; the installer now requires bounded/retriedinstall-depsfor cached non-Chromium or mixed selections. Chromium’s existing fast path/advisory opt-in and cold installation remain unchanged. Executable Bash regressions replace the obsolete blanket cache-skip assumption. This follows Playwright’s CI dependency guidance.Code Concerns
No unresolved findings remain from independent code review. Latest-head main CI passed every quality and preview/Docker/Pages E2E job without test retries. The complete browser workflow passed under the unchanged retry policy, with one retried case per engine as recorded below.
Verification
AbortErrorduring reload, then passed its existing retry. Three focused reruns passed without retries; the abort was not reproduced.scrollIntoViewIfNeeded, then passed its existing retry. The repaired cache-model fixture and native focus regressions passed on their first attempts. These two cases remain recorded as observed flakiness rather than a zero-retry full run.Remote acceptance on latest head
052cead0: main CI, preview smoke, and the explicitly dispatched complete WebKit/Firefox and slow-network workflow all passed. All 31 commits are pushed. The weekly corpus matrix is intentionally excluded from this focused manual browser run; scheduled defaults are unchanged.