🎨 Palette: 숫자 입력 필드 빈 문자열 처리 개선

[seonghobae]

💡 What: target_bytes와 batch_target_bytes 숫자 입력 필드의 inline 유효성 검사 로직에 빈 문자열(empty string) 검사를 추가하여 사용자가 값을 지울 때 오류 메시지가 해제되도록 수정했습니다.
🎯 Why: 빈 문자열을 파싱하면 NaN이 반환되어 기본 HTML5 제약 조건(예: required)이 작동하기 전에 '0보다 커야 합니다'라는 부정확한 오류 메시지가 표시되어 사용자에게 혼란을 줄 수 있었습니다. 이 변경으로 불필요한 오류가 표시되지 않고 자연스러운 입력 경험을 제공합니다.
📸 Before/After: 해당 없음 (동적 검증 시나리오 개선)
♿ Accessibility: 스크린 리더 사용자가 입력란을 비웠을 때 부적절하게 aria-invalid="true"가 유지되는 현상을 방지하여 정확한 폼 상태를 안내합니다.

---

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

[opencode-agent]

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

• Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

• Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

• Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

• Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

• Result: REQUEST_CHANGES

• Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head ce1a5f072dd85c1545491ea9d0251d89aa006a36.

• Head SHA: ce1a5f072dd85c1545491ea9d0251d89aa006a36

• Workflow run: 30586468466

• Workflow attempt: 1

Coverage evidence

Coverage evidence job did not run or did not publish coverage evidence.

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file (2 files)"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file (2 files)"]
  R1 --> V1["required checks"]

Loading

[opencode-agent]

OpenCode Review Overview

• Head SHA: ce1a5f072dd85c1545491ea9d0251d89aa006a36
• Workflow run: 30586468466
• Workflow attempt: 1
• Gate result: REQUEST_CHANGES (approval step)

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

• Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

• Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

• Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

• Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

• Result: REQUEST_CHANGES

• Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head ce1a5f072dd85c1545491ea9d0251d89aa006a36.

• Head SHA: ce1a5f072dd85c1545491ea9d0251d89aa006a36

• Workflow run: 30586468466

• Workflow attempt: 1

Coverage evidence

Coverage evidence job did not run or did not publish coverage evidence.

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file (2 files)"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file (2 files)"]
  R1 --> V1["required checks"]

Loading

[seonghobae]

Closed as a duplicate of #274. #274 contains the complete empty-string reset behavior for both target-size inputs and is the sole current review/auto-merge candidate, avoiding duplicate branch drift and repeated Actions consumption.

[google-labs-jules]

Closed as a duplicate of #274. #274 contains the complete empty-string reset behavior for both target-size inputs and is the sole current review/auto-merge candidate, avoiding duplicate branch drift and repeated Actions consumption.

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