🎨 Palette: [UX improvement] 악보 뷰어 접근성 및 사용성 개선

[seonghobae]

💡 What: 악보 뷰어(ScoreViewer)의 아이콘 전용 버튼(확대/축소, 이전/다음)에 title 툴팁을 추가하고, 모든 관련 컴포넌트(ScoreViewer, ScoreView)에서 네이티브 disabled 대신 aria-disabled를 사용하도록 변경했습니다. 비활성화 시 사용 불가능한 이유를 설명하는 툴팁도 추가했습니다.
🎯 Why: 아이콘만 있는 버튼의 경우 시각 장애인용 스크린 리더에는 aria-label로 읽히지만, 마우스를 사용하는 일반 사용자에게는 의미가 불명확할 수 있습니다. 또한 네이티브 disabled는 툴팁 표시나 마우스 이벤트를 완전히 차단하므로 aria-disabled와 pointer-events 제어 방식을 사용하는 것이 웹 접근성에 유리합니다.
📸 Before/After: 확대/축소 등의 아이콘 버튼 위로 마우스를 올리면 툴팁이 나타나고, 활성 프로젝트가 없어 비활성화된 추가/열기 버튼에도 이유를 설명하는 툴팁이 나타납니다.
♿ Accessibility: 스크린 리더와 키보드 탐색(Tab) 시 비활성 버튼도 접근이 가능하도록 변경되어 맥락을 이해하기 쉽습니다.

---

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

• Head SHA: 31f0bcd7f12dd119d636052d6968f07d48cabf45

• Workflow run: 29764264329

• Workflow attempt: 1

Coverage evidence

Coverage Decision

• Result: FAIL
• Test evidence: not proven passing
• Docstring evidence: not proven passing when configured
• Failure count: 3

Changed-File Evidence Map

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

Loading

[opencode-agent]

OpenCode Review Overview

• Head SHA: 31f0bcd7f12dd119d636052d6968f07d48cabf45
• Workflow run: 29764264329
• 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 31f0bcd7f12dd119d636052d6968f07d48cabf45.

• Head SHA: 31f0bcd7f12dd119d636052d6968f07d48cabf45

• Workflow run: 29764264329

• Workflow attempt: 1

Coverage evidence

Coverage Decision

• Result: FAIL
• Test evidence: not proven passing
• Docstring evidence: not proven passing when configured
• Failure count: 3

Changed-File Evidence Map

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

Loading

[seonghobae]

Closing as closed-obsolete (palette a11y micro-PR storm) by autonomous product-completion loop.

Winner / disposition target: #727

Unique value from this cluster is consolidated there (projectId path guard + npm HIGH CVE pins + Foote novelty kernel sign). Remaining micro-duplicates do not land additional commercial readiness.

[seonghobae]

closed-closed-obsolete (palette a11y micro-PR storm) → #727

[google-labs-jules]

closed-closed-obsolete (palette a11y micro-PR storm) → #727

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

[google-labs-jules]

Closing as closed-obsolete (palette a11y micro-PR storm) by autonomous product-completion loop.

Winner / disposition target: #727

Unique value from this cluster is consolidated there (projectId path guard + npm HIGH CVE pins + Foote novelty kernel sign). Remaining micro-duplicates do not land additional commercial readiness.

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