⚡ Bolt: Cache colors map to reduce allocations

[himattm]

💡 What: Caches the output of colors.ColorMap() within the StatusLine struct using sync.Once.
🎯 Why: The StatusLine previously called colors.ColorMap() every time runPlugin was executed. colors.ColorMap() allocates and returns a new map with 30+ string key-value pairs each time it's called. Since plugins are executed repeatedly (and concurrently), this caused significant, unnecessary garbage collection overhead and map allocation. Caching it eliminates this overhead.
📊 Impact: Reduces memory allocations per plugin execution, resulting in lower GC pressure and slightly improved performance, especially when many plugins are running or the prompt is rendered frequently.
🔬 Measurement: This optimization improves runtime performance by avoiding repeated heap allocations for the map. Tests pass successfully in ~0.9s.

---

PR created automatically by Jules for task 9519186400810483619 started by @himattm

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

[gemini-code-assist]

Code Review

This pull request introduces a caching mechanism for the color map within the StatusLine struct to optimize performance by reducing allocations during plugin execution. The implementation uses sync.Once for thread-safe, lazy initialization. A review comment points out a potential thread-safety risk if plugins modify the shared map and suggests adding documentation to ensure the map is treated as read-only.

[gemini-code-assist]

Caching the color map and sharing it across multiple plugin executions introduces a potential thread-safety issue. Since Go maps are reference types and are not thread-safe for concurrent access if any writer is involved, a native plugin that modifies the Colors map in its Input struct could cause a data race or unexpected side effects for other plugins running concurrently. It is recommended to document that the returned map must be treated as read-only by all consumers.

// getColorsMap returns the cached colors map, initializing it safely if needed.
// The returned map is shared across plugins and must be treated as read-only.
func (sl *StatusLine) getColorsMap() map[string]string {

[himattm]

Closing as superseded by direct commit 42f3149 on main, which consolidated the StatusLine color-map caching optimization without the generated .jules note.

[google-labs-jules]

Closing as superseded by direct commit 42f3149 on main, which consolidated the StatusLine color-map caching optimization without the generated .jules note.

Understood. Acknowledging that this work is now superseded by a direct commit on main and stopping work on this task.