🎨 Palette: 디렉토리 제목 레이아웃 안정성 및 시각적 계층화

[seonghobae]

💡 What: 디렉토리 목록 HTML 상단의 <h1> 제목에 긴 텍스트 줄바꿈 방지(word-break: break-all;) 및 하단 테두리 스타일을 추가하여 시각적 계층 구조를 부여했습니다.
🎯 Why: 띄어쓰기가 없는 매우 긴 디렉토리 이름이 화면 밖으로 넘쳐 레이아웃을 깨뜨리는 문제를 방지하고, 제목과 목록 영역을 명확히 구분하여 가독성을 높이기 위함입니다.
📸 Before/After: 긴 문자열의 제목이 영역을 이탈하지 않고 줄바꿈되며, 목록과 선으로 깔끔히 나뉩니다.
♿ Accessibility: 제목과 내용 간의 시각적인 구조화 강화. 다크 모드 시 적절한 테두리 색상 지원 추가 및 우선순위를 위해 미디어 쿼리 순서 조정.

---

PR created automatically by Jules for task 2232685345308458070 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: 26 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: bd145dc1-08ed-4bc6-b36a-25d9b516fbb8

📥 Commits

Reviewing files that changed from the base of the PR and between 060abbb and 6bab995.

📒 Files selected for processing (3)

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

---

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

[seonghobae]

@coderabbitai review
@cwl-noema-review
@opencode-agent

Review the exact live head only. Verify long unbroken directory titles wrap without horizontal overflow, heading/list hierarchy remains semantically correct, light/dark/high-contrast border behavior is token-consistent, responsive layout and print output are not regressed, and generated HTML/CSS tests cover the change. Require current JVM tests, configured coverage, security gates, and zero unresolved threads. Review only; do not update the branch, merge, release, or alter protections.

[coderabbitai]

Rate Limit Exceeded

@seonghobae have exceeded the limit for the number of chat messages per hour. Please wait 11 minutes and 36 seconds before sending another message.