Repository navigation
Conversation
Preserve failed local writes per storage object until persistence recovers, without changing revision or account boundaries. Add RED-to-GREEN unit and Electron regressions. Retain the first full E2E failure and subsequent unchanged affected-suite results; draft publication awaits full hosted qualification.
7 of 17 tasks
This branch was successfully deployed
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.
When localStorage rejects a Viewed write, the next toggle currently reconstructs state from stale storage: marking B loses A, and a later toggle can resurrect an unmarked file. This retains only failed writes in a storage-object-scoped session fallback, persists accumulated changes on the next successful write, then resumes ordinary storage reads. Account/repository/PR/revision boundaries and the existing 200-PR/3000-path bounds remain. This follows the reproduced #506 review finding and keeps #324’s remaining acceptance gates open.
Four new unit cases and an actual-controls Electron quota case were observed failing against unchanged production code, then passed after the repair. The 22 workspace tests cover session marks/unmarks, denied reads, persistence recovery, separate storage objects, account/revision isolation and bounds. Both Viewed Electron cases passed. One independent read-only review found no Critical or Important code finding; the interim receipt wording has been refreshed with actual results.
Build and typecheck passed; full units passed with 2,583 passes, 36 skips and zero failures/cancellations. The first canonical local desktop E2E run failed: 522 passed, 17 skipped and one existing draft/account-isolation case returned unexpected extra text after an exact fill. Its cause remains unestablished, and its log/trace are retained. The unchanged failed case then passed once in 4.9 seconds; the complete actions/diff specs passed 50 cases in 2.0 minutes, followed by separate site eight and web four passes. Those additional results do not turn the first canonical run green or establish a causal repair. The dated receipt preserves all first failures and scope limits.
Signed source
a92560cfa9be18fde213878b670a2c41955f3246has now passed all twelve source checks, including macOS, Linux/Windows installer builds and the source iPhone suite. The complete source macOS job passed 2,583 units with 36 skips, 526 desktop cases with fourteen skips in 33.1 minutes, eight site cases and four web cases, with zero failures/cancellations or observed retry annotations. All four downloaded artifacts match their API SHA-256 digests and pass ZIP integrity. The tested preview treeb32cf180ef158e58622c40433c61e597a8b597bdis independently reproduced from its recorded parents. A clean projection onto current mainb6e3026changes only two documentation files from that tested source. The original local draft/account anomaly remains unexplained and retained; the fresh complete hosted suite qualifies the current behavior without establishing a causal repair or turning the old run green. The source signature and independently restored recovery bundle remain verified. This PR is still draft; the ready transition and protected queue/actual merge remain pending, and no queue request has been made. Local session fallback does not survive renderer restart while persistence fails, and concurrent-writer convergence is not promised. Native/live/human acceptance, release and default activation remain separate.