Repository navigation
chore(core): promote qualified safe repository connection - #86
Merged
Merged
Conversation
… consent feat(core): prepare safe repository connection and explicit Git write consent
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.
Owns portable checkout locations, scope-specific local markers and one encrypted owner-wide connection intent per repository.
Validation: Owning Rust/Flutter/TypeScript gates passed.42 native GDS tests exercise actual isolated Git clone/adoption/publication, cancellation, scoped markers and concurrent path replacement; both newly found races failed before the fixes and pass afterward. Native Vault and CLI verify original authority, encrypted intent, separate consent, ACK/idempotence and actual synthetic-credential GitHub401 refusal. Final Sharedcffec11 passed full gates and actual GTK consent grant/revoke and Android API36 emulator. Final production HTTPS/WASM browser passed login, encrypted Source, background401, unsupported Git write absence, offline mutation and full reload, automatic ACK/convergence and online reload with no manual synchronization. Positive GitHub credential access remains unverified.
No periodic commit sync activation, relocation, release or deployment. Qualified source:
e052fa0ee00bde55cda24746df2dc07f6ed996e7.