⚡ Bolt: CSS 할당 및 SHA-256 해시 연산 파일 레벨 추출 최적화

[seonghobae]

💡 What

process_dir 함수 내부에 정의되어 있던 정적 CSS 문자열(cssContent)과 이를 이용한 비용이 큰 SHA-256 암호화 해시 연산(styleHash)을 Kotlin 파일의 최상위 속성(Top-level properties)으로 추출했습니다.

🎯 Why

기존 코드에서는 process_dir 함수가 재귀적으로 호출될 때마다 (즉, 순회하는 모든 디렉토리마다) 동일한 100줄짜리 CSS 문자열이 새로 할당되고, 가장 비용이 큰 연산 중 하나인 MessageDigest.getInstance("SHA-256").digest()가 반복적으로 실행되었습니다. 이는 디렉토리가 많아질수록 심각한 CPU 및 메모리 낭비(O(N) 오버헤드)를 유발하는 성능 병목(bottleneck)이었습니다.

📊 Impact

• 성능 향상: 디렉토리당 불필요한 문자열 할당 및 무거운 해시 계산(SHA-256)이 제거되어, 대규모 디렉토리 트리 처리 시 실행 시간이 크게 단축되고 GC 압력이 감소합니다. (O(N) 연산 -> O(1) 연산으로 최적화)
• 커버리지 유지: 최상위 속성의 암시적 getter(implicit getters)에 대한 접근을 검증하는 테스트(testCssPropertiesCoverage)를 추가하여 100% JaCoCo 테스트 커버리지를 유지했습니다.

🔬 Measurement

./gradlew test jacocoTestReport를 실행하여 100% 테스트 커버리지가 유지되고 모든 테스트가 통과하는지 확인할 수 있습니다.

---

PR created automatically by Jules for task 4897936578418658829 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: 21 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: 424cc86a-7bb2-46d1-b0be-1a5ce9ea223d

📥 Commits

Reviewing files that changed from the base of the PR and between a859a11 and 9874b9f.

📒 Files selected for processing (3)

• .jules/bolt.md
• src/main/kotlin/html4tree/main.kt
• src/test/kotlin/html4tree/MainTest.kt

---

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