Repository navigation
feat: retain native observation metadata through audit replay - #1012
Merged
Merged
Conversation
…ve-custody-20261019
…ve-custody-20261019
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.
Retain optional closed native-observation metadata through security-record projection, spill/restart replay and canonical audit JSONL. Raw birth, witness, sequence and capture values remain separate from normalized identity and deliveryId; missing D1 context keeps the raw evidence with identity unavailable. Invalid or oversized metadata preserves the underlying legacy event.
Validation: 106 tests across six suites, including 25 new cases; four assertion mutants killed/restored; actual spill/restart/audit hashing and tamper rejection; scoped lint/format, configured types and independent security/test review passed. Original canonical implementation blobs remain unchanged. Configured types do not establish JS-body checking here.
No producer, source authentication, actor attribution, calibrated time or native loss-range forwarding is added. Runtime admission remains unsupported with zero accepted events. Owner identity review is required before merge.
Integrated by merge from master
ff963d06. Independent integration review and all five required CI checks pass on0c739f0b. The owner confirmed this scoped merge with the stated limits.