⚡ Bolt: O(1) aggregation for job event sequences

[crabcanon]

💡 What: Replaced in-memory array indexing (list_for_job()[-1]) with a direct database aggregation query get_max_sequence_no in JobEventRepository.
🎯 Why: Finding the maximum sequence number by loading up to 1000 events into memory was inefficient, similar to an N+1 query problem, consuming excessive memory and CPU.
📊 Impact: Changes sequence number lookup from O(N) memory/network (bounded to 1000) to an O(1) database aggregation operation, significantly reducing overhead for long-running jobs with many events.
🔬 Measurement: Verified with pytest tests/integration/test_db_foundation.py and checking end-to-end jobs in pytest tests/integration/test_api_e2e.py.

---

PR created automatically by Jules for task 18151184031125641158 started by @crabcanon

[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.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
cortex	Ready	Preview, Comment	Jul 16, 2026 8:04pm