🎨 Palette: 숫자 입력 필드 빈 값 인라인 유효성 검사 개선

[seonghobae]

💡 What: target_bytes와 batch_target_bytes 입력 필드에서 값을 지웠을 때 커스텀 에러(Must be greater than 0.)가 즉시 나타나지 않도록 this.value === ''일 때의 처리를 추가했습니다.
🎯 Why: 사용자가 입력 필드를 지우고 다시 입력하려고 할 때 빈 문자열이 NaN으로 파싱되면서 의도치 않게 에러 메시지가 표시되는 문제를 해결하기 위함입니다. 빈 값일 경우 브라우저의 기본 HTML5 required 유효성 검사에 맡기는 것이 자연스럽습니다.
📸 Before/After: 빈 문자열 입력 시 에러 메시지(Must be greater than 0.)가 즉시 표시되던 것에서, 메시지와 aria-invalid 속성이 즉시 제거되도록 변경.
♿ Accessibility: aria-invalid 속성과 프리셋 버튼의 aria-pressed 상태를 명시적으로 제거함으로써 스크린 리더 사용자에게 불필요하거나 잘못된 에러 상태가 전달되지 않게 개선했습니다.

---

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

• Head SHA: 926d800da296a3226b4c11c400739d6b8d4d927f

• Workflow run: 30570687141

• 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: 926d800da296a3226b4c11c400739d6b8d4d927f
• Workflow run: 30570687141
• 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 926d800da296a3226b4c11c400739d6b8d4d927f.

• Head SHA: 926d800da296a3226b4c11c400739d6b8d4d927f

• Workflow run: 30570687141

• 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. The same two production handlers and learning record are covered by the canonical PR, which now owns the single exact-head CI, security, review, and auto-merge path.

[google-labs-jules]

Closed as a duplicate of #274. The same two production handlers and learning record are covered by the canonical PR, which now owns the single exact-head CI, security, review, and auto-merge path.

알겠습니다. 이 PR이 중복으로 간주되어 종료되었음을 인지하였으며, 이 작업에 대한 진행을 중단하겠습니다.