CI note: the initial checks failed before repository commands ran. The lint and test jobs failed while downloading actions/setup-go@v5; the backend and frontend build jobs failed during checkout with HTTP 403 from GitHub. Local verification completed with:

• go test ./internal/pkg/xregexp
• pnpm exec tsc --noEmit --pretty false
• git diff --check

Greptile Summary

This PR adds (?i) case-insensitive prefix support to the channel model filter UI — fixing a bug where (?i)^gpt-4 was incorrectly flagged as invalid because the old validation used bare new RegExp(val) (which throws on (?i) in JavaScript). The backend already handled this via regexp2 inline modifiers; this PR closes the gap on the frontend.

• pattern.ts: ensureAnchored (returning a string) is replaced by compilePattern (returning a compiled RegExp). splitInlineModifier now extracts the modifier as JS RegExp flags so (?i)^gpt-4 becomes /^(?:gpt-4)$/i. A new exported isValidModelPattern provides clean separation between validation and matching, scoped deliberately to (?i) only.
• channels-action-dialog.tsx: Validation now delegates to isValidModelPattern, which correctly accepts (?i) patterns.
• Locale files & backend tests: Placeholder, description copy, and Go test coverage updated to match the new behaviour.

Confidence Score: 5/5

Safe to merge — the change is a focused, well-scoped fix with no regressions on existing patterns.

The refactor correctly replaces bare new RegExp(val) validation with isValidModelPattern, which translates the modifier into a proper JS i flag before compiling. All existing matching semantics for non-modifier patterns are preserved and the implementation is consistent across validation, matching, locale strings, and backend tests.

No files require special attention.

Important Files Changed

_{Reviews (3): Last reviewed commit: "Support case-insensitive model filter pa..." | Re-trigger Greptile}

有点冲突了