🧹 코드 품질 개선: _process_constraint_group 매개변수 개수 줄이기

[seonghobae]

Outcome

Reduce the private Snowflake constraint helper's parameter list without changing constraint semantics: the existing structured group key now travels as one value and is unpacked at the helper boundary.

Scope

• one production file;
• no dependency or lockfile change;
• no public API, persistence, query, or capability change.

The unrelated generated backend/uv.lock added by the predecessor head has been removed.

Verification

• focused Snowflake introspection suite: 3 passed;
• mypy for app/snowflake_introspect/introspect.py: passed.

Merge boundary

Exact current head: bbe1c3d7824a2db56c12925b0550180fe5a355b0.

Repository CI/security checks and qualifying independent current-head approval remain required.

[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: 47 minutes

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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 within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: e0f4bc6d-baf3-4d34-8b6b-c00b9562a683

📥 Commits

Reviewing files that changed from the base of the PR and between 466e616 and d3bb824.

⛔ Files ignored due to path filters (3)

• backend/requirements-dev.lock is excluded by !**/*.lock
• backend/requirements.lock is excluded by !**/*.lock
• frontend/package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (8)

• .github/workflows/ci.yml
• CHANGELOG.md
• backend/app/snowflake_introspect/introspect.py
• backend/pyproject.toml
• docs/doctoring/search-identity-and-sequential-polling.md
• frontend/package.json
• frontend/src/App.searchPolling.test.tsx
• frontend/src/App.tsx

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{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 bbe1c3d7824a2db56c12925b0550180fe5a355b0.

• Head SHA: bbe1c3d7824a2db56c12925b0550180fe5a355b0

• Workflow run: 31700700469

• Workflow attempt: 1

Coverage evidence

Coverage Decision

• Result: FAIL
• Test evidence: not proven passing
• Docstring evidence: not proven passing when configured
• Failure count: 1

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Backend: introspect.py"]
  S1 --> I1["API and service runtime"]
  I1 --> R1["Review risk: Backend: introspect.py"]
  R1 --> V1["backend tests"]

Loading

[opencode-agent]

OpenCode Review Overview

• Head SHA: bbe1c3d7824a2db56c12925b0550180fe5a355b0
• Workflow run: 31700700469
• 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 bbe1c3d7824a2db56c12925b0550180fe5a355b0.

• Head SHA: bbe1c3d7824a2db56c12925b0550180fe5a355b0

• Workflow run: 31700700469

• Workflow attempt: 1

Coverage evidence

Coverage Decision

• Result: FAIL
• Test evidence: not proven passing
• Docstring evidence: not proven passing when configured
• Failure count: 1

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Backend: introspect.py"]
  S1 --> I1["API and service runtime"]
  I1 --> R1["Review risk: Backend: introspect.py"]
  R1 --> V1["backend tests"]

Loading

[seonghobae]

@OpenCode review

Please review exact current head 26bcdc2 after normal update to protected main. Re-evaluate this PR on this head only; do not transfer predecessor evidence. Current-head checks are queued.

[seonghobae]

@OpenCode review

Please review exact current head 77064d5 only; automation superseded the previous requested head. Do not transfer predecessor evidence. Current-head checks are queued.

[seonghobae]

@OpenCode review

Please review exact current head 26b35a9. Re-evaluate this head only; do not transfer predecessor approvals or check evidence. Current-head required checks are still queued.

[seonghobae]

Closed as superseded by the broader #814 constraint-context refactor. Both branches carry the same stale search/polling stack and conflict with main; #814 is the canonical implementation for this code-health change.

[seonghobae]

Closed as duplicate of #814.

[google-labs-jules]

Closed as superseded by the broader #814 constraint-context refactor. Both branches carry the same stale search/polling stack and conflict with main; #814 is the canonical implementation for this code-health change.

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

[google-labs-jules]

Closed as duplicate of #814.

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