Repository navigation
feat(context): preserve private tool metadata in event custody - #998
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.
Preserve optional private tool-context metadata through supported event routing, live deduplication, canonical audit and security spill/replay. Closed enum/byte/candidate limits reject raw payloads, and incomplete evidence downgrades association without changing OS actor attribution or discarding the underlying event.
Validation: independent security/test-quality reviews passed; R2 covered 247 affected tests and the final test-only revision passed 30 focused cases, including complete persisted/exported capsules, exact delivery IDs and capsule-only hash-chain tamper detection. Revision-specific mutation/restoration receipts are retained. Transcript selection, trusted session verification, clock calibration, live production and UI integration remain separate; this does not complete W4.