⚡ Optimize live results array generation

[artosien]

💡 What: Replaced Array.from({ length: 6 }, ...).sort(...) with a pre-allocated array (new Array(6)) and a standard for loop, followed by an inline .sort().

🎯 Why: The previous approach generated a new array inside the map callback of a setInterval loop. Array.from incurs additional object allocation and iterator protocol overhead, negatively affecting performance for frequent updates.

📊 Measured Improvement:
Created a focused benchmark to verify the performance difference:

Baseline: Array.from with sort x 539,581 ops/sec ±5.57%
Optimization: Loop with sort x 1,481,765 ops/sec ±6.09%
Change over baseline: ~2.7x improvement in ops/sec.

---

PR created automatically by Jules for task 10307777446501470346 started by @artosien

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