🎨 Palette: 빈 디렉토리 상태의 시각적 메타포 개선

[seonghobae]

💡 What: 빈 디렉토리를 나타내는 상태 메시지의 아이콘을 정보 아이콘(ℹ)에서 열린 폴더 아이콘(📂)으로 변경했습니다.
🎯 Why: 일반적인 정보 아이콘보다 빈 폴더 아이콘이 "여기에 파일이나 디렉토리가 없다"는 컨텍스트를 사용자에게 훨씬 더 직관적으로 전달하는 훌륭한 시각적 메타포로 작동하기 때문입니다.
📸 Before/After: N/A (Visual icon change from ℹ to 📂)
♿ Accessibility: 유지됨. role="status" 및 텍스트 렌더링에 영향 없음.

---

PR created automatically by Jules for task 8417503028751057540 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:25 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: 803f6bb4-d9b7-4695-92fd-306c759cceb6

📥 Commits

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

📒 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]

Closing as superseded by draft canonical #360 and the protected base. The current page already exposes the empty state with role="status", flex alignment, and a decorative icon. #360 owns the remaining evidence-based light/dark contrast, separators, focus/hover treatment, reduced-motion, browser tests, WCAG 2.2 doctoring, and changelog after #363. Replacing one emoji with another is not retained because glyph shape and accessibility behavior vary by platform; deterministic markup should be used only when a tested semantic need exists. No evidence from this overlapping head is reused.

[google-labs-jules]

Closing as superseded by draft canonical #360 and the protected base. The current page already exposes the empty state with role="status", flex alignment, and a decorative icon. #360 owns the remaining evidence-based light/dark contrast, separators, focus/hover treatment, reduced-motion, browser tests, WCAG 2.2 doctoring, and changelog after #363. Replacing one emoji with another is not retained because glyph shape and accessibility behavior vary by platform; deterministic markup should be used only when a tested semantic need exists. No evidence from this overlapping head is reused.

Understood. Acknowledging that this work is superseded and stopping work on this task.