⚡ Bolt: 반복적인 정적 문자열 해싱 오버헤드 제거

[seonghobae]

💡 What: CSS_CONTENT, STYLE_HASH, CSS_BLOCK 등 정적인 문자열 할당 및 해시 연산을 process_dir 루프 내부에서 파일 최상단 전역 스코프로 추출했습니다.
🎯 Why: 디렉토리를 순회할 때마다 변하지 않는 CSS 문자열을 생성하고 복잡한 SHA-256 암호화 해싱을 반복적으로 수행하여 불필요한 GC 오버헤드와 CPU 낭비가 발생하고 있었습니다.
📊 Impact: 해시 연산과 할당이 O(N)에서 O(1)로 변경되어, 디렉토리 트리가 깊고 넓어질 수록 렌더링 속도가 크게 향상되고 메모리 사용량이 절감됩니다.
🔬 Measurement: ./gradlew test jacocoTestReport를 통해 100% 테스트 커버리지가 유지되고 기능이 정확히 동일함을 확인할 수 있습니다.

---

PR created automatically by Jules for task 11442510430081834954 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: 48 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: caa52d37-5d5e-48b0-a4ce-bdb5cbf56ce0

📥 Commits

Reviewing files that changed from the base of the PR and between a32b065 and 098712a.

📒 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.}

[seonghobae]

Closing as superseded by #362. Both changes hoist the immutable CSS block and SHA-256 digest out of process_dir; #362 keeps those implementation details private, is based on the current protected branch, and has successful exact-head CI/security evidence.

[google-labs-jules]

Closing as superseded by #362. Both changes hoist the immutable CSS block and SHA-256 digest out of process_dir; #362 keeps those implementation details private, is based on the current protected branch, and has successful exact-head CI/security evidence.

Understood. Acknowledging that this work is now superseded by #362 and stopping work on this task.