⚡ Optimize log appending with an O(1) circular buffer

[Trapston3]

💡 What: Replaced the O(N) logBuffer.unshift() logic with a pre-allocated fixed-size circular buffer. Reads reconstruct the array chronologically via a new getLogs() helper.

🎯 Why: Every time a new request came in, the server unshifted a new entry to an array, causing an O(N) copy operation. This was a significant CPU bottleneck on the critical hot path of request serving. By using a circular buffer with a pre-allocated array and tracking a current index, writing logs is now an O(1) operation.

📊 Measured Improvement:
In synthetic benchmarks, writing to the buffer improved by ~10x:

• Original Unshift Write (5M ops): ~600ms
• Circular Buffer Write (5M ops): ~60ms
• Mixed Workload (1M writes, 10K reads): ~184ms -> ~19ms (nearly 10x improvement overall).

Reads are technically slightly slower (as it reconstructs the array), but since reads (API requests for logs) happen vastly less frequently than writes (every HTTP request), this is a massive net performance win. Correctness remains identical (newest logs first).

---

PR created automatically by Jules for task 17759002116881125762 started by @Trapston3

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