🎨 Palette: [UX improvement] 클라이언트 측 파일 크기 제한 동적 안내 및 일괄 업로드 검증 강화

[seonghobae]

💡 What: 하드코딩된 '5 GiB' 에러 메시지를 MAX_UPLOAD_BYTES 기반으로 동적으로 계산하여 표시하도록 개선하고, 일괄 업로드 시 총 용량 제한에 대한 즉각적인 클라이언트 측 인라인 에러 피드백을 추가했습니다.\n🎯 Why: 서버 측 용량 제한 상수가 변경될 경우 잘못된 정보가 안내될 위험을 방지하며, 사용자가 일괄 업로드 시 대기하기 전에 즉시 용량 초과 사실을 알 수 있게 하여 사용자 경험을 향상시킵니다.\n📸 Before/After: 파일 선택 시 용량이 초과될 경우 즉시 해당 파일 용량과 동적 제한 값이 포함된 에러 메시지가 붉은색으로 표시됩니다.\n♿ Accessibility: 용량 초과 시 setCustomValidity와 함께 aria-invalid='true' 속성을 즉시 부여하여 스크린 리더 사용자에게도 실시간으로 오류 상태를 명확히 전달합니다.

---

PR created automatically by Jules for task 16228037417279580643 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: 17 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: 870c8a45-4538-4496-8957-d00b32977b26

📥 Commits

Reviewing files that changed from the base of the PR and between 5a92586 and c6fac07.

📒 Files selected for processing (4)

• .jules/palette.md
• CHANGELOG.md
• saas_web.py
• tests/test_saas_web.py

---

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

[seonghobae]

Superseded by merged PR #354, which includes the same dynamic upload-limit text and aggregate batch-size prevalidation with passing exact-head checks. Closing this duplicate to reduce redundant review and Actions load.

[google-labs-jules]

Superseded by merged PR #354, which includes the same dynamic upload-limit text and aggregate batch-size prevalidation with passing exact-head checks. Closing this duplicate to reduce redundant review and Actions load.

Understood. Acknowledging that this work is now obsolete and stopping work on this task.