🎨 Palette: 새로고침 버튼 UX 및 접근성 개선

[seonghobae]

이번 PR은 화면의 작은 UX 및 접근성 개선을 포함합니다.

• 긴 처리 시간을 가질 수 있는 "새로고침(Refresh)" 버튼의 상태를 HTML의 disabled 속성 대신 aria-disabled="true"로 처리하여 스크린 리더와 키보드 초점을 유지합니다.
• 로딩 상태를 시각적으로 보여주기 위해 스피너 애니메이션을 추가하였습니다.
• 외부 창이나 새 탭으로 열리는 링크에 화면에만 보이지 않는(Screen reader only) 안내 텍스트((opens in a new tab))를 추가하여 스크린 리더 사용자의 혼란을 방지하였습니다.
• 관련된 내용을 .jules/palette.md 파일에 기록하였습니다.

---

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

[Copilot]

Pull request overview

UI/UX 및 접근성 관점에서 Viewer 화면의 “Refresh” 상호작용과 새 탭으로 열리는 링크의 컨텍스트 전달을 개선하는 PR입니다. 비동기 작업 중 버튼의 포커스 유지(aria-disabled)와 로딩 스피너 표시, 새 탭 안내용 SR-only 텍스트를 추가합니다.

Changes:

• Refresh 버튼을 disabled 대신 aria-disabled로 제어하고 로딩 스피너를 표시
• 새 탭으로 열리는 링크에 (opens in a new tab) SR-only 안내 문구 추가 및 rel="noopener noreferrer" 적용
• 관련 접근성/UX 가이드를 .jules/palette.md에 기록

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.

File	Description
src/main/resources/static/assets/viewer/viewer.js	Refresh 버튼 상태/스피너 처리 및 새 탭 링크 라벨(SR-only) 추가
src/main/resources/static/assets/viewer/viewer.css	aria-disabled 스타일, 스피너 애니메이션, sr-only 유틸리티 클래스 추가
src/main/java/com/clearfolio/viewer/controller/ViewerUiController.java	Open JSON bootstrap 링크를 새 탭 + SR-only 안내로 개선
.jules/palette.md	disabled vs aria-disabled 및 새 탭 안내에 대한 팀 학습/액션 기록

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[opencode-agent]

Pull request overview

OpenCode reviewed the current-head evidence but cannot approve because required coverage evidence did not pass.

Findings

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove 100% test and docstring coverage

• Problem: The OpenCode approval path reached an APPROVE control result while the separate coverage-evidence job result was failure.

• Root cause: Automated approval is only valid when the same-head coverage-evidence job proves both test coverage and docstring coverage at 100%, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, unsupported-tooling, or partial coverage evidence is a blocker.

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

• Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE.

• Result: REQUEST_CHANGES

• Reason: coverage-evidence result was failure, so 100% test/docstring coverage was not proven for current head 976195e483314fbb4e3d43ce8484e125f46b0d2d.

• Head SHA: 976195e483314fbb4e3d43ce8484e125f46b0d2d

• Workflow run: 28331295520

• Workflow attempt: 1

Coverage evidence

Coverage Evidence

• Head SHA: 976195e483314fbb4e3d43ce8484e125f46b0d2d
• Required test coverage: 100%
• Required docstring coverage: 100%

Python test coverage

============================= test session starts ==============================
platform linux -- Python 3.12.3, pytest-9.1.1, pluggy-1.6.0
rootdir: /home/runner/work/clearfolio/clearfolio
configfile: pyproject.toml
collected 13 items

scripts/ci/test_opencode_review_normalize_output.py .............        [100%]

============================== 13 passed in 0.21s ==============================

• Result: PASS

Python coverage threshold

Name                                                  Stmts   Miss  Cover
-------------------------------------------------------------------------
scripts/ci/opencode_review_normalize_output.py          133      1    99%
scripts/ci/test_opencode_review_normalize_output.py     122      0   100%
-------------------------------------------------------------------------
TOTAL                                                   255      1    99%
Coverage failure: total of 99 is less than fail-under=100

• Result: FAIL (exit 2)

Python docstring coverage

RESULT: FAILED (minimum: 100.0%, actual: 39.1%)

• Result: FAIL (exit 1)

Coverage Decision

• Result: FAIL
• Test coverage: not proven 100%
• Docstring coverage: not proven 100%
• Failure count: 2

[opencode-agent]

OpenCode Review Overview

• Head SHA: 976195e483314fbb4e3d43ce8484e125f46b0d2d
• Workflow run: 28331295520
• Workflow attempt: 1
• Gate result: REQUEST_CHANGES (approval step)

Pull request overview

OpenCode reviewed the current-head evidence but cannot approve because required coverage evidence did not pass.

Findings

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove 100% test and docstring coverage

• Problem: The OpenCode approval path reached an APPROVE control result while the separate coverage-evidence job result was failure.

• Root cause: Automated approval is only valid when the same-head coverage-evidence job proves both test coverage and docstring coverage at 100%, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, unsupported-tooling, or partial coverage evidence is a blocker.

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

• Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE.

• Result: REQUEST_CHANGES

• Reason: coverage-evidence result was failure, so 100% test/docstring coverage was not proven for current head 976195e483314fbb4e3d43ce8484e125f46b0d2d.

• Head SHA: 976195e483314fbb4e3d43ce8484e125f46b0d2d

• Workflow run: 28331295520

• Workflow attempt: 1

Coverage evidence

Coverage Evidence

• Head SHA: 976195e483314fbb4e3d43ce8484e125f46b0d2d
• Required test coverage: 100%
• Required docstring coverage: 100%

Python test coverage

============================= test session starts ==============================
platform linux -- Python 3.12.3, pytest-9.1.1, pluggy-1.6.0
rootdir: /home/runner/work/clearfolio/clearfolio
configfile: pyproject.toml
collected 13 items

scripts/ci/test_opencode_review_normalize_output.py .............        [100%]

============================== 13 passed in 0.21s ==============================

• Result: PASS

Python coverage threshold

Name                                                  Stmts   Miss  Cover
-------------------------------------------------------------------------
scripts/ci/opencode_review_normalize_output.py          133      1    99%
scripts/ci/test_opencode_review_normalize_output.py     122      0   100%
-------------------------------------------------------------------------
TOTAL                                                   255      1    99%
Coverage failure: total of 99 is less than fail-under=100

• Result: FAIL (exit 2)

Python docstring coverage

RESULT: FAILED (minimum: 100.0%, actual: 39.1%)

• Result: FAIL (exit 1)

Coverage Decision

• Result: FAIL
• Test coverage: not proven 100%
• Docstring coverage: not proven 100%
• Failure count: 2

Change Flow DAG

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Workflow (3 files)"]
  S1 --> I1["GitHub Actions review job"]
  I1 --> R1["Review risk: Workflow (3 files)"]
  R1 --> V1["actionlint plus required checks"]
  Evidence --> S2["Changed file (7 files)"]
  S2 --> I2["repository behavior"]
  I2 --> R2["Review risk: Changed file (7 files)"]
  R2 --> V2["required checks"]
  Evidence --> S3["CI script (10 files)"]
  S3 --> I3["review and security gate shell path"]
  I3 --> R3["Review risk: CI script (10 files)"]
  R3 --> V3["bash -n plus Strix self-test"]

Loading

[seonghobae]

중복 정리(2차): 'async 버튼 로딩/비활성화' 클러스터 중복 → 정본 #71 유지. 동일 목적/파일로 동시 병합 불가. 고유 변경은 #71에 반영하거나 재오픈.

[google-labs-jules]

중복 정리(2차): 'async 버튼 로딩/비활성화' 클러스터 중복 → 정본 #71 유지. 동일 목적/파일로 동시 병합 불가. 고유 변경은 #71에 반영하거나 재오픈.

알겠습니다. 이 작업이 중복으로 간주되어 종료됨을 확인했습니다.