🛡️ Sentinel: [MEDIUM] Fix control character validation in schema names

[seonghobae]

🚨 심각도 (Severity): MEDIUM
💡 취약점 (Vulnerability): DiagramViewCreateIn, TableAnnotationUpsertIn, ApiKeyCreateIn 모델의 문자열 입력 필드(이름 등)에 제어 문자(Control characters) 필터링이 누락되어 있었습니다.
🎯 영향 (Impact): 악의적인 사용자가 제어 문자(\x00, \n 등)를 포함시켜 로그 주입(Log Injection) 또는 Null Byte Injection 공격을 시도할 수 있습니다.
🔧 수정 사항 (Fix): Pydantic Field에 정규식 pattern=r"^[^\x00-\x1F\x7F]+$"를 추가하여 제어 문자가 포함된 입력을 엄격하게 차단했습니다.
✅ 검증 (Verification): 백엔드에서 uv run pytest 명령을 통해 모든 스키마 유효성 검사 테스트 및 382개의 전체 테스트가 성공적으로 통과되었음을 확인했습니다.

---

PR created automatically by Jules for task 11512627887590114853 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: 44 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: d988cb46-9662-44f1-a16f-748bb0bbfda4

📥 Commits

Reviewing files that changed from the base of the PR and between 72afe6d and 59524c3.

📒 Files selected for processing (3)

• .jules/sentinel.md
• backend/app/schemas.py
• backend/tests/test_schema_validation.py

---

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

[seonghobae]

Closing as superseded by focused PR #699 for DiagramViewCreateIn.name, TableAnnotationUpsertIn.schema_name, relation_name, and ApiKeyCreateIn.key_name. #699 contains the same printable-character contract without the transient .jules file and already has exact-head CI, Security Scan, Semgrep, auto-merge, and current-head review requests.

The additional ApplySqlIn.sql change is not safely bundled here: SQL is intentionally multiline and permits tab/newline/CR while rejecting a different control-character set, so that parser/input boundary needs its own focused tests, CHANGELOG/doctoring evidence, and current-main PR rather than riding a duplicate name-validation branch. No check or review evidence transfers to that future slice.

[google-labs-jules]

Closing as superseded by focused PR #699 for DiagramViewCreateIn.name, TableAnnotationUpsertIn.schema_name, relation_name, and ApiKeyCreateIn.key_name. #699 contains the same printable-character contract without the transient .jules file and already has exact-head CI, Security Scan, Semgrep, auto-merge, and current-head review requests.

The additional ApplySqlIn.sql change is not safely bundled here: SQL is intentionally multiline and permits tab/newline/CR while rejecting a different control-character set, so that parser/input boundary needs its own focused tests, CHANGELOG/doctoring evidence, and current-main PR rather than riding a duplicate name-validation branch. No check or review evidence transfers to that future slice.

Understood. Acknowledging that this PR is closed as superseded and the ApplySqlIn change requires a separate, focused PR. Stopping work on this task.