Repository navigation
Send Security run notifications without private write-ups - #562
Merged
Merged
Conversation
Preserve Security notifications for advisory and private issue records. Retain titles and private links, match fingerprints in issue bodies, and keep write-ups out of notifications. Add an end-to-end regression covering notifications for existing open and closed issues alongside newly recorded findings.
This was referenced Oct 8, 2026
Merged
Merged
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.
Summary
Keep recorded finding metadata through partial recording failures. Detailed Security audit failure causes remain in local logs because verifier commands and Harness diagnostics can contain private write-up.
Closes #539
Evidence
a_completed_security_audit_sends_one_notification_when_askedfailed with zero Resend requests.After: one request with the Security run outcome and recipient.
After: both exact commands passed, and both tests remain in
tests/security_run.rs:cargo check,cargo fmt --check,cargo clippy --all-targets -- -D warnings, and the fullCARGO_BUILD_JOBS=2 cargo testpassed (1532 tests passed, 1 ignored, zero failures). The Security run suite passed all 24 tests.Testing seams
Unaddressed findings
Standards
None. The one ADR 0015 privacy finding was reproduced and fixed.
Spec
None. The one #539 confidentiality finding was reproduced and fixed.
Both reviewers read all 10 changed files. Changed files left unread: none under Standards or Spec. Review fixed point:
issue-427at8b775669cb8bbc1bbd815428337ac587477d2151(remote branch pinned after fetch; the local branch was stale).Merge Danger
Door: two-way
Reverting restores the previous Security notification behavior; no migration or stored-record change.
Blast Radius: notifications
Security runs now honor the existing email defaults and checks. A delivery error remains a warning; skipped runs send none.
Built with codex · gpt-6.1-sol · xhigh