🛡️ Sentinel: [CRITICAL] ERD DDL 생성 시 SQL 인젝션 방지 기능 추가

[seonghobae]

ERDModel의 DDL 생성 기능에서 컬럼 타입 정의를 통한 SQL 인젝션 공격(예: '; DROP TABLE...')을 방지하기 위해 타입 내 세미콜론(;) 사용을 차단하는 검증 로직을 추가했습니다.

---

PR created automatically by Jules for task 3741588731625752870 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: 19 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: 06943f0a-7019-4b59-9fcc-bdad2a383cf5

📥 Commits

Reviewing files that changed from the base of the PR and between 9ef092b and 2353382.

📒 Files selected for processing (3)

• .jules/sentinel.md
• packages/web/src/lib/erd.test.ts
• packages/web/src/lib/erd.ts

---

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

[seonghobae]

Superseded by #397. This branch is the earlier semicolon-only ERD DDL guard; #397 on the newer base replaces that narrow token check with positive SQL-type/default grammar validation, identifier/foreign-key validation, post-validation mutation protection, and broader adversarial tests. Closing the stale competing security path; no prior checks or reviews transfer.

[google-labs-jules]

Superseded by #397. This branch is the earlier semicolon-only ERD DDL guard; #397 on the newer base replaces that narrow token check with positive SQL-type/default grammar validation, identifier/foreign-key validation, post-validation mutation protection, and broader adversarial tests. Closing the stale competing security path; no prior checks or reviews transfer.

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