🎨 Palette: 네이티브 다크 모드 HTML 리포트 지원 추가

[seonghobae]

💡 What

생성되는 HTML 리포트의 review-required와 review-clear 클래스 테두리 색상을 시스템의 다크 모드 설정에 맞춰 조정할 수 있도록 네이티브 다크 모드를 지원했습니다.

🎯 Why

기존에는 CSS가 color-scheme: light dark;로 설정되어 있었음에도 불구하고, 중요한 알림을 담당하는 두 클래스의 왼쪽 테두리 색상(#9c2f1f와 #357a38)이 하드코딩되어 있었습니다. 이 때문에 사용자가 OS 수준에서 다크 모드를 사용할 경우 검정색 배경에서 매우 낮은 명도 대비를 보여 시인성과 접근성이 크게 떨어지는 문제가 있었습니다.

📸 Before/After

(Playwright 테스트 스크립트를 통해 생성된 스크린샷 참조)

• Before: 다크 모드 배경에서 매우 짙고 어두운 빨강 및 초록 테두리.
• After: 다크 모드 감지 시, var(--review-required)와 var(--review-clear)를 사용하여 각각 #e57373과 #81c784 등 훨씬 밝고 명확하게 구별되는 색상으로 변환.

♿ Accessibility

다크 모드를 선호하는 사용자나 저시력 사용자가 시각적으로 중요한 '리뷰 필요' 및 '리뷰 불필요' 상태를 보다 쉽고 명확하게 파악할 수 있게 되었습니다. WCAG 색상 대비 요건에 부합하는 개선사항입니다.

---

PR created automatically by Jules for task 6517764978165083871 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

@opencode-agent[bot], you've reached your PR review limit, so we couldn't start this review.

Next review available in: 14 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 8a075382-7a1e-4f62-bc3c-c0df55a0b739

📥 Commits

Reviewing files that changed from the base of the PR and between b14fe3d and 87dbd06.

📒 Files selected for processing (2)

• python/fast_mlsirm/scoring/essay/report_html.py
• tests/test_scoring_essay_report_html.py

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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