Skip to content

fix(devlog): stop the audit record from breaking its own privacy gate #2177

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lidge-jun merged 1 commit into from
Aug 20, 2026
+7 −3
Merged

fix(devlog): stop the audit record from breaking its own privacy gate #2177

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions devlog/_plan/260820_bug_pr_backlog_consolidation/100_release_audit.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,10 +36,15 @@ The sanitizer on that path is not sufficient, for two independent reasons — bo
the shipped code, not reasoned about:

```
"gpt-5.6-luna\nBearer sk-abc123def456ghi789jkl" -> "gpt-5.6-lunaBearer [REDACTED]"
"gpt-5.6-luna\nAIzaSyA1B2C3D4E5F6G7H8I9J0K1L2M3N4O5P6" -> unchanged, key intact
"<prefix>\n<Bearer + an sk-shaped value>" -> control stripped, value redacted
"<prefix>\n<a Google AIza-shaped key>" -> control stripped, value INTACT
```

(Written as shapes rather than literals on purpose: `scripts/privacy-scan.ts` matches those
patterns wherever they appear, so pasting a real-looking transcript breaks the `gates` job for
every branch cut from `dev`. That is precisely what #2175 had to undo, and this record
reintroduced it — the scanner does not care that a credential is fake.)

1. Control characters are stripped **before** redaction, so the newline that separated marker
from credential is gone by the time the `Bearer` rule looks for a word boundary.
2. The runtime redactor is a deny-list. An `AIza`-shaped Google key has no rule and survives.
Expand Down Expand Up @@ -191,4 +196,3 @@ this closeout resolves them; they need a product decision, not a patch.

Release execution remains unauthorized: no `scripts/release.ts`, no publish, no tag, no change
to `main` or `preview`.

Loading