🎨 Palette: [UX improvement] ERD 캔버스 메타데이터 입력 및 JSON 백업/복원 기능 추가

[seonghobae]

💡 What

• EditTableModal 내 컬럼 항목에 코멘트(column_comment) 및 예시값(example_value) 텍스트 입력 필드를 추가하였습니다.
• EditTableModal 내 컬럼 항목의 순서를 위/아래로 변경할 수 있는 '위로/아래로 이동' 버튼을 추가하였습니다.
• 캔버스 툴바에 현재 ERD 상태(노드 및 엣지)를 .json 파일로 내보내는 버튼(📤)과 파일을 불러오는 버튼(📥)을 추가하였습니다.

🎯 Why

• 데이터 딕셔너리로서의 완성도를 높이기 위해 ERD 편집기 내에서 각 컬럼의 코멘트와 예시값을 직접 수정할 필요가 있습니다.
• 컬럼 순서 변경 기능은 데이터베이스 스키마 설계 시 컬럼을 논리적으로 그룹화하고 시각적으로 정렬하는 데 필수적인 UX입니다.
• JSON 불러오기/내보내기 기능은 변경된 다이어그램을 로컬 환경에 오프라인 백업하거나, 다른 사용자와 직접 파일을 통해 공유 및 복원할 수 있도록 지원합니다.

📸 Before/After

• Before: 컬럼 코멘트 및 예시값 편집이 불가능했으며, 컬럼 순서를 변경하려면 스크립트 수정이나 DB 재정렬이 필요했습니다. ERD 캔버스는 이미지나 SQL 등으로만 내보낼 수 있었습니다.
• After: 컬럼에 대한 상세 메타데이터 입력과 순서 변경이 편집 모달에서 즉각적으로 가능하며, 캔버스 상태를 그대로 담은 JSON 파일을 가져오거나 내보낼 수 있습니다.

♿ Accessibility

• 새롭게 추가된 코멘트 및 예시값 텍스트 인풋에 각각 고유한 aria-label을 부여하여 스크린 리더에서 식별할 수 있도록 개선하였습니다.
• 위로/아래로 이동 버튼에 aria-label과 title 속성을 적절히 부여하고, 사용 불가능한 상태(최상단/최하단)일 경우 명시적인 disabled 속성을 부여하여 탭 순서와 시각적 포커스에서 자연스럽게 배제되도록 처리하였습니다.
• JSON 불러오기 버튼은 시각적으로는 이모지(📥)로 보이나, input type="file"이 포함된 label 컨테이너에 올바른 aria-label을 지정하여 키보드 탐색과 포커스가 지원되도록 구성하였습니다.

---

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

• Head SHA: b21fd5ce4ce9cb1c85cf26413370628d9195f287

• Workflow run: 29764021294

• 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["Frontend (4 files)"]
  S1 --> I1["browser runtime and bundle"]
  I1 --> R1["Review risk: Frontend (4 files)"]
  R1 --> V1["frontend tests"]

Loading

[opencode-agent]

OpenCode Review Overview

• Head SHA: b21fd5ce4ce9cb1c85cf26413370628d9195f287
• Workflow run: 29764021294
• 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 b21fd5ce4ce9cb1c85cf26413370628d9195f287.

• Head SHA: b21fd5ce4ce9cb1c85cf26413370628d9195f287

• Workflow run: 29764021294

• 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["Frontend (4 files)"]
  S1 --> I1["browser runtime and bundle"]
  I1 --> R1["Review risk: Frontend (4 files)"]
  R1 --> V1["frontend tests"]

Loading

[seonghobae]

Closed as superseded/duplicate Palette a11y PR; keyboard/form a11y baseline already on main (#568/#567/#534). Remaining a11y land via priority PR or follow-up if needed.

[google-labs-jules]

Closed as superseded/duplicate Palette a11y PR; keyboard/form a11y baseline already on main (#568/#567/#534). Remaining a11y land via priority PR or follow-up if needed.

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