[UX 개선] EmailDetail 데스크탑 및 모바일 UI 보강

[seonghobae]

💡 무엇을: EmailDetail UI 보강
🎯 왜: 디자인 QA 반영
📸 변경 전/후: 데스크탑/모바일 밀도 및 사용성 개선
♿ 접근성: 유지

---

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

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

Next review available in: 21 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 9acfb39f-b6c3-4541-9790-854af978d908

📥 Commits

Reviewing files that changed from the base of the PR and between be3bedb and 97d6477.

📒 Files selected for processing (4)

• CHANGELOG.md
• docs/doctoring/email-detail-responsive-action-surface.md
• frontend/src/components/EmailDetail.test.tsx
• frontend/src/components/EmailDetail.tsx

---

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

[github-actions]

PR governance metadata gate update for 97d6477a78cdef738af5c9e32b66786c2ade6466: no current blocking failures remain.

PR governance metadata gate is ready; all current-head requirements passed.

[seonghobae]

Superseded by maintainer-owned replacement #1245. The replacement is an exact one-commit, four-file reconstruction on current develop and must establish fresh exact-head Checks and review evidence; the action_required runs and approval on this Jules lineage are not reused.

[google-labs-jules]

Superseded by maintainer-owned replacement #1245. The replacement is an exact one-commit, four-file reconstruction on current develop and must establish fresh exact-head Checks and review evidence; the action_required runs and approval on this Jules lineage are not reused.

Understood. Acknowledging that this PR is superseded by #1245 and stopping work on this task.

[seonghobae]

Superseded by maintainer-owned four-file reconstruction #1245 on current develop, which preserves the validated responsive email-detail evidence and calendar writeback-intent behavior while obtaining executable GitHub Actions jobs. Keep this predecessor closed; do not reuse its action_required state as evidence.

[google-labs-jules]

Superseded by maintainer-owned four-file reconstruction #1245 on current develop, which preserves the validated responsive email-detail evidence and calendar writeback-intent behavior while obtaining executable GitHub Actions jobs. Keep this predecessor closed; do not reuse its action_required state as evidence.

Understood. Acknowledging that this PR is superseded by #1245 and stopping work on this task.