Repository navigation
Fix Hub summary privacy, connector recovery, and accessible states - #192
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
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.
A synthetic Hub journey reproduced Anchor document fields appearing in default summary responses and a Live connector network failure turning the entire private Hub into HTTP 500. Default Anchor reads now project summary metadata while explicit sensitive reads and sync replay preserve full records. Live summary network/JSON errors use the existing unavailable state. Each app card now exposes its visible count/date or unavailable state as its accessible description.
Validation: baseline Worker suite and disposable aggregation/replay/account-isolation journey; 11 focused regressions passed. An initial full check caught a test-only Env typing mismatch, which is corrected. The final local full check was blocked before execution by Fleet's disk budget; this PR's Worker and Swift CI jobs provide final validation. No bindings, migrations, credentials, or cross-app writes change.