🎨 Palette: 빈 디렉토리 상태 메시지 접근성 개선 (role="status")

[seonghobae]

💡 What: 생성된 HTML의 빈 디렉토리 안내 메시지 요소(<div class="empty-dir">)에 role="status" 속성을 추가했습니다. 테스트 코드(testGoEmptyDir)에 대한 검증 내용도 업데이트하여 100% 테스트 커버리지를 유지했습니다.
🎯 Why: 비어 있는 디렉토리를 안내하는 텍스트가 일반 텍스트로만 렌더링되어, 스크린 리더 사용자가 해당 요소에 포커스를 직접 맞추지 않으면 내용이 비어 있음을 인지하기 어려웠습니다.
📸 Before/After:

• Before:<div class="empty-dir">이 디렉토리는 비어 있습니다.</div>
• After:<div class="empty-dir" role="status">이 디렉토리는 비어 있습니다.</div>
  ♿ Accessibility: 상태를 나타내는 텍스트에 ARIA role="status" 속성을 명시하여, 스크린 리더 등 보조 기기가 상태 변화를 동적으로 안내하도록 접근성을 개선했습니다.

---

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

• Head SHA: f572e012c521fc0884bcb3210b8aa1bf5e85ed95

• Workflow run: 30424220797

• 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 (3 files)"]
S1 --> I1["repository behavior"]
I1 --> R1["Review risk: Changed file (3 files)"]
R1 --> V1["required checks"]

Loading

[opencode-agent]

OpenCode Review Overview

• Head SHA: f572e012c521fc0884bcb3210b8aa1bf5e85ed95
• Workflow run: 30424220797
• 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 f572e012c521fc0884bcb3210b8aa1bf5e85ed95.

• Head SHA: f572e012c521fc0884bcb3210b8aa1bf5e85ed95

• Workflow run: 30424220797

• 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 (3 files)"]
S1 --> I1["repository behavior"]
I1 --> R1["Review risk: Changed file (3 files)"]
R1 --> V1["required checks"]

Loading

[seonghobae]

Closing as superseded by the protected branch: role="status" and its generated-page assertion are already present. Draft #360 is the canonical post-#363 path for remaining tested visual/accessibility refinement. No stale check or review is reused.

[google-labs-jules]

Closing as superseded by the protected branch: role="status" and its generated-page assertion are already present. Draft #360 is the canonical post-#363 path for remaining tested visual/accessibility refinement. No stale check or review is reused.

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