⚡ Bolt: Offload blocking UI operations to worker threads

[EffortlessSteven]

💡 What:
Wrapped synchronous file I/O operations (like load_all_specs, fs::read_to_string) in tokio::task::spawn_blocking within the async UI handlers (dashboard, graph_view, flows_view, coverage_view).

🎯 Why:
The previous implementation performed heavy synchronous I/O directly in the async request handlers, blocking the Tokio reactor thread and degrading concurrency under load.

📊 Impact:
Improved responsiveness and throughput by offloading blocking operations to a dedicated thread pool, allowing the async runtime to handle more concurrent requests.

🔬 Measurement:
Verified with cargo test -p http-platform. Ensure the dashboard and other UI pages load correctly without errors.

---

PR created automatically by Jules for task 10963195946350168141 started by @EffortlessSteven

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

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[coderabbitai]

Summary by CodeRabbit

Release Notes

• Refactor

  • View components (dashboard, graph, flows, coverage) updated with improved error handling and fallback mechanisms for missing configuration and status data.

• Dependencies

  • Added Tokio to workspace configuration.

• Documentation

  • Technical documentation on async patterns added.

Walkthrough

Blocking I/O operations (file reads) are offloaded from async Axum handlers to dedicated threads using tokio::task::spawn_blocking. Multiple UI view functions—dashboard, graph_view, flows_view, and coverage_view—are refactored to perform synchronous file operations asynchronously, with comprehensive error handling and fallbacks.

Changes

Cohort / File(s)	Summary
Documentation & Configuration .Jules/bolt.md, crates/http-platform/Cargo.toml	Lesson documentation added on blocking I/O in async handlers; Tokio workspace dependency configured for the http-platform crate.
UI Handler Refactoring crates/http-platform/src/ui.rs	Dashboard, graph_view, flows_view, and coverage_view functions refactored to spawn blocking tasks for file I/O. Adds error handling with graceful fallbacks; metadata loading, JSON/Markdown parsing, and graph generation now execute on dedicated thread pool rather than async executor thread.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐰 Hop, hop, files now flow,
No more blocking in async's glow!
Spawn and wait on threads so true,
UI renders swift and new! ✨

---

Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull request overview

This PR addresses a performance issue by offloading blocking file I/O operations from async request handlers to dedicated worker threads. The implementation wraps synchronous operations like load_all_specs, fs::read_to_string, and other spec loading functions in tokio::task::spawn_blocking across all UI handlers in the http-platform crate.

Changes:

• Wrapped blocking I/O in spawn_blocking for all UI handlers (dashboard, graph_view, flows_view, coverage_view)
• Added tokio workspace dependency to http-platform crate
• Documented the pattern in .Jules/bolt.md for future reference

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
crates/http-platform/src/ui.rs	Refactored all UI handler functions to use tokio::task::spawn_blocking for file I/O operations, with proper error handling and logging for join failures
crates/http-platform/Cargo.toml	Added tokio workspace dependency required for spawn_blocking functionality
.Jules/bolt.md	Added documentation explaining the blocking I/O issue and the spawn_blocking solution pattern

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.