⚡ Bolt: [성능 개선] 불변 문자열 및 해시 연산 호이스팅

[seonghobae]

💡 What: process_dir 내의 cssContent와 styleHash 계산을 최상위 private val로 호이스팅했습니다.
🎯 Why: 디렉토리를 순회할 때마다 정적 문자열을 할당하고 SHA-256 해시를 재계산하는 불필요한 오버헤드를 방지하기 위함입니다.
📊 Impact: 다수의 디렉토리 크롤링 시 CPU 주기와 메모리 할당을 크게 절감할 수 있습니다.
🔬 Measurement: ./gradlew clean test jacocoTestReport를 통해 모든 기능이 정상 작동하며 커버리지가 유지됨을 확인했습니다.

---

PR created automatically by Jules for task 714492556351793449 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: 1 minute

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: a5550b13-31d4-46c8-9980-8ea400ddb9b9

📥 Commits

Reviewing files that changed from the base of the PR and between 669c4ef and 55bc58c.

📒 Files selected for processing (2)

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

---

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

[seonghobae]

Closing as superseded by #362. Both move the immutable CSS block and SHA-256 calculation out of process_dir; #362 is the current protected-base, private-surface implementation with successful exact-head CI, Security Scan, and Semgrep evidence.

[google-labs-jules]

Closing as superseded by #362. Both move the immutable CSS block and SHA-256 calculation out of process_dir; #362 is the current protected-base, private-surface implementation with successful exact-head CI, Security Scan, and Semgrep evidence.

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