테스트 커버리지 100% 달성 및 누락된 테스트 추가

[seonghobae]

이 PR은 프론트엔드 코드베이스의 누락된 테스트 브랜치를 수정하여 100% 테스트 커버리지를 달성합니다. GroupModal, EditEdgeModal, prisma 익스포트 기능 등에 대한 구체적인 edge case 시나리오가 추가되었습니다.

---

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

[coderabbitai]

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 4 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 179b1711-d4a2-4a3f-9c44-5f65d2685fda

📥 Commits

Reviewing files that changed from the base of the PR and between 72afe6d and 9d627b2.

📒 Files selected for processing (5)

• .jules/missing-features.md
• frontend/src/components/modals/EditEdgeModal.test.tsx
• frontend/src/components/modals/GroupModal.test.tsx
• frontend/src/components/modals/ModalCoverage.test.tsx
• frontend/src/erd/__tests__/prisma.test.ts

---

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

[seonghobae]

Closing as superseded and behaviorally stale. The branch reintroduces tests that require window.confirm inside EditEdgeModal and GroupModal, while the current correctness repair in #693 centralizes destructive confirmation in the App orchestration layer to prevent duplicate prompts. Its Prisma missing-handle and dangling-target cases are already covered or being strengthened in #700/#693, and the transient .jules/missing-features.md is not the authoritative doctoring/CHANGELOG path. Merging this PR would lock in the wrong UI boundary and create conflicts without adding a distinct production capability.

[google-labs-jules]

Closing as superseded and behaviorally stale. The branch reintroduces tests that require window.confirm inside EditEdgeModal and GroupModal, while the current correctness repair in #693 centralizes destructive confirmation in the App orchestration layer to prevent duplicate prompts. Its Prisma missing-handle and dangling-target cases are already covered or being strengthened in #700/#693, and the transient .jules/missing-features.md is not the authoritative doctoring/CHANGELOG path. Merging this PR would lock in the wrong UI boundary and create conflicts without adding a distinct production capability.

Understood. Acknowledging that this PR is superseded and stopping work on this task. I will not proceed with any further modifications or test changes on this branch.