Repository navigation
Check OPFS capabilities only for default storage - #105
Merged
Merged
Conversation
This was referenced Sep 14, 2026
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.
Sessions with a supplied dense or sparse store now require only engine runtime capabilities; default OPFS sessions retain their early typed persistence checks and backend probe. Both opening paths snapshot the selected store before asynchronous work.
Luna XHIGH implemented; separate fresh Astra MEDIUM records attempt-1 PASS. Focused session 45/45, full check 367/367, 14 adversarial probes and packed Chromium browser/OPFS checks pass. Linux WebKit lacks OPFS APIs even on a blank secure isolated page, so the existing macOS OPFS workflow remains required before delivery.
Tracks #102. Published availability will be delivered through the existing #95 release cut; this source PR does not claim a new registry package.