From 35ab42b627d4e1d0eb7bc769d688f5bcb9a38827 Mon Sep 17 00:00:00 2001 From: bitkyc08-arch Date: Thu, 20 Aug 2026 13:29:55 +0900 Subject: [PATCH] fix(devlog): unbreak privacy:scan on dev The audit record committed in 0637a3548 pasted a reproduction transcript containing a literal "Bearer " line. scripts/privacy-scan.ts matches that shape regardless of whether the value is a real credential, so dev's own release gate has been failing since that commit -- and it fails for every PR branched from dev, not just for the file that introduced it. The value was a placeholder from a local reproduction, not a real secret, but the scanner cannot know that and should not have to. Describing the header instead of pasting it keeps the finding legible and the gate green. --- .../100_release_safety_audit.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/devlog/_plan/260820_bug_pr_backlog_consolidation/100_release_safety_audit.md b/devlog/_plan/260820_bug_pr_backlog_consolidation/100_release_safety_audit.md index 2152c743d2..8ee286d849 100644 --- a/devlog/_plan/260820_bug_pr_backlog_consolidation/100_release_safety_audit.md +++ b/devlog/_plan/260820_bug_pr_backlog_consolidation/100_release_safety_audit.md @@ -27,7 +27,7 @@ and the adapter forwarded our own proxy secret. Reproduced through the real adap ``` URL: https://chatgpt.com/backend-api/codex/responses -AUTH: Bearer ocx_data_this_is_our_proxy_key +AUTH: Bearer LEAKED: true ``` @@ -120,4 +120,3 @@ Version line on `dev` is `2.27.0`, equal to the published `latest` and the `v2.2 pre-release state, not a half-finished bump. This remains a readiness record. No release was executed. -