⚡ Bolt: [performance improvement] CSS 및 해시 캐싱

[seonghobae]

💡 What: 반복 호출되는 process_dir 내에서 고정된 CSS 문자열과 SHA-256 해시 연산을 최상위 private val 상수로 추출했습니다.
🎯 Why: process_dir가 디렉토리마다 호출될 때마다 불필요하게 객체를 할당하고 해시 연산을 수행하는 오버헤드를 방지하기 위해서입니다.
📊 Impact: 디렉토리 크롤링 시 반복적인 객체 생성 및 비용이 큰 해시 연산을 회피하여 메모리 할당 및 실행 속도가 향상됩니다.
🔬 Measurement: Jacoco 테스트 커버리지 및 전체 디렉토리 대상 실행 시간을 비교하여 검증할 수 있습니다.

---

PR created automatically by Jules for task 17877839056247626900 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: 29 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: 5d7f45c3-d8a8-42f9-b276-57d7cbc1057a

📥 Commits

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

📒 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 #363. The same stylesheet/hash caching is canonical there, with the additional exact emitted-byte CSP fix, independent product regression, APA 7 doctoring, changelog, and fresh current-head CI/coverage/security evidence. No result from this duplicate head is reused.

[google-labs-jules]

Closing as superseded by #363. The same stylesheet/hash caching is canonical there, with the additional exact emitted-byte CSP fix, independent product regression, APA 7 doctoring, changelog, and fresh current-head CI/coverage/security evidence. No result from this duplicate head is reused.

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