⚡ Bolt: [performance improvement] Optimize SplitFlapDisplay rendering

[nickdesi]

💡 What: Replaced text.split('').map(...) with a single-pass for loop in SplitFlapDisplay.tsx.
🎯 Why: .split('') creates an intermediate array of single-character strings on every render. For a component heavily reused in lists and tables (like a departures board), this creates significant memory churn and garbage collection overhead.
📊 Impact: Eliminates an unnecessary array allocation per render per split-flap display, reducing GC pressure and memory usage in hot paths.
🔬 Measurement: Verify rendering performance in the React Profiler on the DeparturesBoard/List, or trace memory allocations in the Chrome DevTools Memory tab.

---

PR created automatically by Jules for task 7657676021002322381 started by @nickdesi

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

[github-actions]

🤖 Revue automatique par l'IA (gemini-2.5-flash)

Verdict : ✅ Approuvé

Cette PR introduit une micro-optimisation pertinente dans SplitFlapDisplay.tsx en remplaçant l'anti-pattern text.split('').map(...) par une boucle for directe. Cette modification réduit l'allocation de tableaux intermédiaires et la pression sur le ramasse-miettes, ce qui est particulièrement bénéfique pour un composant potentiellement rendu de nombreuses fois. L'explication dans .jules/bolt.md est claire et technique, justifiant parfaitement le changement. Le code est propre et atteint l'objectif d'amélioration des performances.

Revue générée automatiquement.