Repository navigation
feat(hooks): add private owned configuration transactions - #1017
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.
Add a private transaction session around the existing hook planner. An exact review ticket gates backup/readback, target revalidation, guarded provider write and postwrite verification. Removal preserves unrelated edits; uncertain mutation retains backups and locks further writes.
Validation: 90 tests (40 writer and 50 planner); twelve assertion mutants killed/restored; main types with @ts-check, scoped lint/format and independent source/security/test-evidence reviews passed. Three frozen source hashes survived merge-master integration; derived counts updated.
No filesystem provider, production caller, profile discovery, IPC/UI, policy routing or hook activation. The IO marker identifies an interface, not native qualification. Real identity/compare-write, external-writer coordination, callback bounds, private-storage durability and recovery remain required. Configured does not establish observation or blocking.