Repository navigation
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
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.
Summary
bloom-synctransaction engine for authenticated Ed25519 save bundlesbloomctl syncgrammar and makebloom-network-sync statusreport engine readiness without starting transport or listenersThis slice deliberately provides no cloud/provider/transport implementation and opens no network listener.
Verification
8077e94481c202a93f64d512a05bbf7c85384952: all primary and external owners completed;ci-build [READY!]9ce3b5ddb148382f39ac15fc4d9e0b0963248574: 3/3a9fd690627738985a016cb7df824574d6de14b4c: native, AddressSanitizer, 850-test shell, static analysis, and clean ARM all passedDevice gate
Risk 3 / Warm. No SYNC-02 candidate was deployed. The signed UI-12 candidate from #644 remains the sole installed testing candidate and still needs the user's physical observation of normal shutdown text and actual power-off. After that gate, this PR still requires its own signed Mini Plus candidate deployment, structured health/feature evidence, cleanup, rollback verification, and any required physical validation before merge.
Closes #650