⚡ Bolt: 디렉토리 처리 루프 내 정적 에셋 객체 추출을 통한 성능 개선

[seonghobae]

💡 What: 매번 디렉토리 순회 시(process_dir) 불필요하게 생성되던 정적 CSS 콘텐츠, HTML 태그, 그리고 SHA-256 해시 계산을 루프 밖의 private object(StaticAssets)로 분리하고 상수로 정의했습니다.
🎯 Why: 큰 상수 문자열의 할당과 비싼 해시 연산을 디렉토리 처리 수만큼 반복하는 것은 무의미한 CPU와 메모리의 소모를 발생시킵니다.
📊 Impact: 큰 디렉토리 트리 순회 시 객체 할당 오버헤드와 SHA-256 연산을 캐싱(초기 1회)함으로써 불필요한 시스템 자원 낭비를 방지하고 전체 처리 속도를 향상시킵니다.
🔬 Measurement: JaCoCo Coverage 100% 만족 여부 및 복잡한 디렉토리 구조에서의 소요시간 단축을 통한 성능 모니터링 확인

---

PR created automatically by Jules for task 6746548488645544555 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: 38 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: 7cd5d569-b603-4151-a49c-ec74d1e46cca

📥 Commits

Reviewing files that changed from the base of the PR and between a32b065 and 6e5ad1a.

📒 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. This PR and #362 implement the same static CSS/hash hoisting. #362 is the newer two-file protected-base change and has already passed exact-head CI, Security Scan, and Semgrep, so retaining both would duplicate review and merge work.

[google-labs-jules]

Closing as superseded by #362. This PR and #362 implement the same static CSS/hash hoisting. #362 is the newer two-file protected-base change and has already passed exact-head CI, Security Scan, and Semgrep, so retaining both would duplicate review and merge work.

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