🧪 redact_sensitive_log 테스트 추가

[seonghobae]

🎯 What:
scripts/ci/redact_sensitive_log.py 스크립트에 대한 단위 테스트가 누락되어 있어 이를 보완하기 위해 100% 테스트 커버리지를 제공하는 테스트 스위트를 추가했습니다.

📊 Coverage:

• 빈 문자열 및 None 입력에 대한 처리
• 줄바꿈 문자열(\n, \r\n)의 보존 확인
• 유효한 JSON 문자열 내의 재귀적 마스킹 처리 확인
• 비정형 텍스트 내의 토큰 패턴(GH 토큰, AWS 키 등) 마스킹 처리 확인
• 선형 탐색을 통한 키-값 할당(key=value, key: value) 마스킹 처리
• 토큰 파싱 에지 케이스 및 빈 값 처리
• JWT 및 Bearer 토큰 문자열 마스킹 확인
• 스크립트 메인 진입점 및 SystemExit 처리 시나리오 확인

✨ Result:
redact_sensitive_log.py의 모든 분기 로직과 에지 케이스에 대해 100% 코드 커버리지가 달성되어 리팩토링 시 안전성이 확보되었습니다. 또한 mypy, bandit, interrogate 등의 정적 분석 도구 검증을 완료하였습니다.

---

PR created automatically by Jules for task 137040798574166017 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: 59 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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: 0dc10e4f-9d1e-4fd6-8865-859644a4f5fd

📥 Commits

Reviewing files that changed from the base of the PR and between 6eb06cd and 029a587.

📒 Files selected for processing (2)

• .Jules/palette.md
• tests/test_redact_sensitive_log.py

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[seonghobae]

RCA/feasibility: closing unmerged as superseded by the active redaction security branch #842. #842 now changes scripts/ci/redact_sensitive_log.py itself, wires it through both sandbox consumers, and owns exact-head security regressions across test_sandboxed_log_redaction_regression.py, test_sandboxed_verify.py, test_sandboxed_web_e2e.py, and OpenCode security boundaries. Its current source-tree contract reports 605 statements / 206 branches at 100% across the shared redactor and wrappers, including JSON/JWT/authorization/private-key/assignment/terminal-control/pathological-input cases. A separate current-main test-only branch for the pre-#842 redactor would immediately diverge and require reconciliation while adding no distinct uncovered production defect. Keep coverage ownership with the security branch that changes and validates the implementation.

[google-labs-jules]

RCA/feasibility: closing unmerged as superseded by the active redaction security branch #842. #842 now changes scripts/ci/redact_sensitive_log.py itself, wires it through both sandbox consumers, and owns exact-head security regressions across test_sandboxed_log_redaction_regression.py, test_sandboxed_verify.py, test_sandboxed_web_e2e.py, and OpenCode security boundaries. Its current source-tree contract reports 605 statements / 206 branches at 100% across the shared redactor and wrappers, including JSON/JWT/authorization/private-key/assignment/terminal-control/pathological-input cases. A separate current-main test-only branch for the pre-#842 redactor would immediately diverge and require reconciliation while adding no distinct uncovered production defect. Keep coverage ownership with the security branch that changes and validates the implementation.

Understood. Acknowledging that this work is now obsolete and stopping work on this task.