perf: implement L1 caching in heavyComputation

[shenald-dev]

• Modifies heavyComputation in src/index.js to track lastIterations and lastResult.
• Bypasses Map get, delete, and set operations if the current iterations matches lastIterations.
• Updates L1 cache variables during Map hits and complete cache misses.
• Appends learning to .jules/bolt.md.

---

PR created automatically by Jules for task 1536097787376758441 started by @shenald-dev

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

[shenald-dev]

The L1 cache implementation looks correct for a single-threaded context. If heavyComputation could be invoked concurrently, consider making the cache variables thread-safe (e.g., using atomic operations or a lock) to avoid race conditions.

Reviewed — quality: high

[shenald-dev]

Looks good, merging this in. CI is green and everything checks out 👍

Add L1 caching to heavyComputation to skip recomputation when iterations unchanged.

[google-labs-jules]

The L1 cache implementation looks correct for a single-threaded context. If heavyComputation could be invoked concurrently, consider making the cache variables thread-safe (e.g., using atomic operations or a lock) to avoid race conditions.

Reviewed — quality: high

Node.js runs standard execution (like heavyComputation) on a single main thread, so we don't have to worry about traditional threading race conditions here for the L1 cache variables. If we ever moved this to Worker Threads, they would get their own isolated module scope anyway. The current implementation is safe.

[google-labs-jules]

Looks good, merging this in. CI is green and everything checks out 👍

Add L1 caching to heavyComputation to skip recomputation when iterations unchanged.

Acknowledged.