Repository navigation
Include BeatBrowser task recovery in local installations - #14
Merged
Merged
Conversation
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
1 participant
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.
Pin the included BeatBrowser to the revision that preserves background tasks across extension reloads and browser restarts. Users retain progress and completed states, while unfinished tasks restore paused with explicit missing-page association and agent reconnection.
Validation: frozen-lockfile installation, lint, browser-lab tests (20 passed), and local setup script tests passed. Prepared the bundled extension and verified its recovery module is present. BeatBrowser itself passed 267 tests, package/security/syntax checks, and isolated real Chromium reload/restart tests. No database or running daily browser connection was changed.