🎨 Palette: 비동기 버튼 로딩 상태 개선 (조직 모달)

[seonghobae]

💡 What: 조직 생성 및 삭제 모달의 완료(제출) 버튼에 비동기 처리 중임을 나타내는 스피너(Loader2)를 추가했습니다.
🎯 Why: 텍스트 변경(예: '생성 중…')만으로는 진행 상황이 눈에 띄지 않을 수 있어, 스피너를 통해 사용자에게 명확한 시각적 피드백을 제공하고자 합니다.
📸 Before/After: 버튼 텍스트 좌측에 회전하는 스피너 아이콘 추가
♿ Accessibility: 스피너 아이콘에 aria-hidden="true"를 적용하여 스크린 리더에서 불필요한 정보가 읽히지 않도록 처리했습니다.

---

PR created automatically by Jules for task 16180310049095241756 started by @seonghobae

Summary by CodeRabbit

• 개선 사항
  • 조직 생성 및 삭제 요청 중 버튼에 회전하는 로딩 아이콘을 표시합니다.
  • 작업 진행 상태를 시각적으로 전달해 더 명확하고 접근성 높은 사용자 경험을 제공합니다.

[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.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 353becf5-468a-4a4a-a04b-bd8f1526e4a4

📥 Commits

Reviewing files that changed from the base of the PR and between a5be9b0 and 4a7698e.

📒 Files selected for processing (3)

• .Jules/palette.md
• packages/web/src/components/org/create-org-modal.tsx
• packages/web/src/components/org/delete-org-modal.tsx

---

📝 Walkthrough

Walkthrough

조직 생성 및 삭제 모달의 요청 진행 중 버튼에 회전형 Loader2 아이콘을 추가했습니다. 비동기 제출 버튼의 로딩 상태 표시 지침도 문서에 기록했습니다.

Changes

조직 모달 로딩 상태

Layer / File(s)	Summary
비동기 버튼 로딩 표시 .Jules/palette.md, packages/web/src/components/org/create-org-modal.tsx, packages/web/src/components/org/delete-org-modal.tsx	조직 생성 및 삭제 요청 중 버튼에 회전형 Loader2 아이콘을 표시합니다. 비동기 제출 버튼에 로딩 스피너를 사용하는 지침을 추가했습니다.

Estimated code review effort: 1 (Trivial) | ~5 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	제목은 조직 모달의 비동기 버튼 로딩 상태 개선이라는 주요 변경 사항을 명확하게 설명합니다.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch palette-async-button-spinners-16180310049095241756

---

_{Comment @coderabbitai help to get the list of available commands.}

[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 4a7698e298758165daeea9e60a476447cc591bec.

• Head SHA: 4a7698e298758165daeea9e60a476447cc591bec

• Workflow run: 31296534181

• 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: 4a7698e298758165daeea9e60a476447cc591bec
• Workflow run: 31296534181
• 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 4a7698e298758165daeea9e60a476447cc591bec.

• Head SHA: 4a7698e298758165daeea9e60a476447cc591bec

• Workflow run: 31296534181

• 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