Repository navigation
Complete native language owners, legacy recovery and measured vault admission - #209
Merged
Merged
Conversation
…gvault-native-bindings
sidmohan0
changed the title
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.
Core's optional native Node/Python packages now use the maintained Rust FogVault owner for approved saves, lock/reopen, conversation state and uncertain-save reconciliation. The browser importer authenticates the existing reference backup formats before approved recovery into fresh FogVault storage. These remain unpublished 0.0.0 candidates; Core beta.3 packages and the Rust 1.88 floor are unchanged.
Near-capacity native measurements showed 197.64 MiB peak RSS with one pending review versus 865.39 MiB with 32. All integrated owners now reject a second pending change before cloning Core, releasing admission on discard, consumption, abandonment or close. Browser cleanup also prevents collected wrappers leaving hidden WASM candidates. Raw Core APIs are unchanged.
Shared dfv scopes verify actual installed npm/wheel/browser packages, current source and archive/installed-file identities, Node → Python → Node on one SQLite vault, and legacy recovery across both envelope versions and credential methods. Future v1 publication requires exact-commit success from all six joint native/browser and three native-language CI scopes.
Local component validation passes: native 11, installed Node 11/Python 18, cross-language round trip, browser 13 each on Chromium/Firefox, legacy importer 8 each on Chromium/Firefox, type checks, verifier/release negative tests and strict Rust checks. Windows CI exposed a UTF-8 fixture-reading issue; its harness fix also passes an isolated non-UTF-8 locale reproduction. Final CI qualifies the complete combined tree, including Edge.
The documented reference importer does not establish Josh's shipping archive provenance or native legacy import. Device/aggregate-memory budgets, production host/provider/security acceptance, final v1 API/schema freeze and public package distribution remain release gates. See docs/integrations/fogvault.md.
Includes the preserved commits from #210 and #211 so qualification covers the complete combination.