Repository navigation
fix: preserve structured capture during secret redaction - #493
Merged
Merged
Conversation
Generated-By: gpt-6.2-sol
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.
Intent
Closes #435
Redact secrets before storing Observation payloads without converting structured values into strings.
Read first
src/functions/privacy.tsandsrc/functions/observe.tstest/capture-redaction.test.tscovers the capture path.Decisions
Out of scope
Verified
npm run build,npm run skills:check,npm run typecheck,npm test,npm run eval:gate, andnpm run eval:gate:rulespassed in an isolated checkout; generated hooks were unchanged.Not verified
Merge danger
Door: One-way for new captures: redacted text is not recoverable on revert.
Blast radius: Observation capture, storage, and downstream consumers of raw payloads.