⚡ Bolt: Zero-Allocation Asset Streaming

[ford442]

Bottleneck: "Was allocating THREE.Vector3 instances per frame via .clone() and math chaining inside updatePredictiveLoading, causing GC spikes and frame drops during streaming operations."\n\nFix: "Implemented a shared _scratchFuturePos THREE.Vector3 scratch variable at the module level. Restructured the predictive math to utilize in-place mutation methods (.copy, .multiplyScalar, .add) to achieve a zero-allocation footprint within the hot path."\n\nImpact: "Eliminated per-frame object instantiations in predictive loading, significantly reducing GC pressure and stabilizing framerate while maintaining seamless continuous asset streaming."

---

PR created automatically by Jules for task 9265640054029750759 started by @ford442

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