🎨 Palette: [접근성 개선] 커스텀 버튼에 명확한 키보드 포커스 상태 추가

[seonghobae]

💡 What

no-organization-state.tsx 컴포넌트의 텍스트형 로그아웃 버튼과 admin-dashboard.tsx 컴포넌트의 고객(Customer) 목록 리스트 아이템 버튼에 키보드 탭(Tab) 네비게이션 시 포커스를 명확히 표시하는 focus-visible 상태 스타일을 추가했습니다.

🎯 Why

<Button> 원형(primitive)을 쓰지 않고 <button> 태그를 직접 스타일링하여 사용하는 커스텀 인터랙티브 요소들에서, hover 시의 시각적 피드백은 제공되나 키보드 포커스 시의 상태 표시가 누락되어 있었습니다. 이로 인해 키보드 내비게이션(Tab) 사용자나 스크린 리더 사용자가 현재 위치를 명확히 파악하기 어려웠습니다.

📸 Before/After

포커스 상태(Tab 키를 눌러 포커스를 맞춘 상태)에서:

• Before: 포커스가 어디에 있는지 전혀 보이지 않거나 브라우저 기본 아웃라인이 깨져서 보임.
• After: 버튼 주위에 테마에 맞는 부드러운 포커스 링(ring-2 ring-ring)이 표시됨.

♿ Accessibility

• 마우스 없이 키보드만으로 탐색하는 사용자가 현재 어느 버튼을 선택하고 있는지 직관적으로 알 수 있게 되어 사용성이 크게 향상되었습니다.

---

PR created automatically by Jules for task 3707331578992569052 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: 8 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: cae6bb32-c689-4573-bbf3-5fdd6cd39c36

📥 Commits

Reviewing files that changed from the base of the PR and between 9ef092b and dc13816.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (12)

• .Jules/palette.md
• .claude/skills/persuasion-review/scripts/probe_harness.py
• .jules/sentinel.md
• .pnpmfile.cjs
• package.json
• packages/cli/src/__tests__/transcript.test.ts
• packages/cli/src/commands/status.ts
• packages/cli/src/lib/inject-agent-hooks.ts
• packages/cli/src/lib/project.ts
• packages/web/package.json
• packages/web/src/components/admin/admin-dashboard.tsx
• packages/web/src/components/dashboard/no-organization-state.tsx

---

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