⚡ Bolt: [성능 개선] SQLite 연결 시 중복되는 PRAGMA 실행 제거

[seonghobae]

💡 What: PRAGMA journal_mode=WAL을 각 데이터베이스 연결(_connect())마다 실행하지 않고, 초기화(__init__) 시에 executescript를 사용하여 스키마와 함께 단 한 번만 실행하도록 변경했습니다.
🎯 Why: WAL 모드는 데이터베이스 파일별로 영구적으로 유지되므로, 매 연결마다 반복 실행할 필요가 없습니다. 이는 불필요한 I/O와 쿼리 파싱 오버헤드를 줄여 짧은 주기로 여러 연결이 발생하는 애플리케이션의 성능을 향상시킵니다.
📊 Impact: 연결당 쿼리 실행 횟수가 감소하여, 특히 동시 연결이 많은 작업(job polling 등)에서 SQLite 성능 향상을 기대할 수 있습니다 (~6% 속도 향상 예상).
🔬 Measurement: sqlite3 연결 반복 테스트를 통해 이전과 이후의 수행 시간을 비교하여 성능 향상을 확인할 수 있습니다. 테스트 슈트도 모두 통과합니다.

---

PR created automatically by Jules for task 12567705094589831940 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: 17 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: 287d7b94-3864-4466-8573-1eacd1a8281f

📥 Commits

Reviewing files that changed from the base of the PR and between 963291f and e62c9e2.

📒 Files selected for processing (3)

• .jules/bolt.md
• CHANGELOG.md
• job_store.py

---

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