⚡ Bolt: [performance improvement]

[google-labs-jules]

💡 What: Replaced LINQ .Concat([item]).ToList() and .ToList() calls in NetworkSimulationEngine.AllocateProportionallyFromNode with manually pre-sized List<string> instances initialized to list.Count + 1 and populated using explicit for loops via array indexers.

🎯 Why: In iterative/recursive "hot paths", utilizing .Concat([item]).ToList() generates massive memory allocations because it requires creating a new enumerator object, closures/delegates, and intermediate array allocations on every invocation. As network scale increases and recursion deepens, this GC pressure becomes a major execution bottleneck. Manually pre-sizing and copying with indexers eliminates all these hidden overheads while achieving the exact same result.

📊 Impact: Substantially decreases the number of managed allocations, directly reducing Garbage Collector execution pauses during large, highly-branching network simulations.

🔬 Measurement: This optimization can be verified using .NET memory profilers (like dotMemory or Visual Studio Profiler) while running complex network scenarios. The allocation footprint of AllocateProportionallyFromNode should see a severe reduction, specifically in array and IEnumerable enumerator classes. All unit tests (dotnet test) continue to pass.

---

PR created automatically by Jules for task 6363237647955043651 started by @wnj00524

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