⚡ Bolt: redact_sensitive_log.py 파싱 루프 및 정규식 성능 개선

[seonghobae]

💡 What: CI 로그에 포함된 민감 정보를 가려내는 scripts/ci/redact_sensitive_log.py 내의 정규식 순회 처리 및 문자별 치환 구조를 최적화했습니다.
🎯 Why: 반복적으로 긴 로그를 검색할 때 각각의 정규식을 순회 적용하고 개별 문자를 리스트에 추가하면 O(N)의 무거운 오버헤드가 누적됩니다.
📊 Impact: 정규식 패턴을 |로 하나로 묶어 엔진 통과 횟수를 줄이고(4회 -> 1회), 문자열 개별 할당을 슬라이스 기반 일괄 복사로 대체하여 로그 파싱 루프 시간을 대폭 단축합니다.
🔬 Measurement: 변경 전과 동일하게 100% 테스트 커버리지를 통과함을 확인했습니다.

---

PR created automatically by Jules for task 2961456267270499281 started by @seonghobae

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[coderabbitai]

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 38 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: a7299416-0f7f-4e5a-9951-7dabb08f054e

📥 Commits

Reviewing files that changed from the base of the PR and between 2a83043 and 820b0a6.

📒 Files selected for processing (2)

• .jules/bolt.md
• scripts/ci/redact_sensitive_log.py

---

_{Comment @coderabbitai help to get the list of available commands.}

[seonghobae]

Superseded by #701 current head c5c52135833d6525c39a8af1f6f6508037a86105, which consolidates the skip-index parser, unmatched-text chunk batching, a single provider-token regex pass, and adversarial base-equivalence/no-leak tests.

[google-labs-jules]

Superseded by #701 current head c5c52135833d6525c39a8af1f6f6508037a86105, which consolidates the skip-index parser, unmatched-text chunk batching, a single provider-token regex pass, and adversarial base-equivalence/no-leak tests.

알겠습니다. 이 작업이 다른 PR(#701)로 대체되었음을 확인했으며, 본 작업을 중단하겠습니다.