⚡ Bolt: [performance improvement] Enable virtualization for Activity Log history

[NITISH-R-G]

💡 What: Replaced ListView + Column with CustomScrollView + SliverList.builder in SosActivityLogScreen.
🎯 Why: The previous implementation wrapped an unbounded history list inside a Column within a ListView. This defeated Flutter's list virtualization, causing all history items to be rendered simultaneously (O(N) rendering). This led to significant UI jank when opening the activity log screen if the user had many saved incidents.
📊 Impact: Reduces rendering time complexity from O(N) to O(1) for visible items. Memory usage and first-paint time will remain flat regardless of how many incidents are stored in history.
🔬 Measurement: Run the app, populate the activity history with dozens of incidents, and open the Activity Log screen. It will load instantly without frame drops, whereas the previous implementation would stall.

---

PR created automatically by Jules for task 6759895365242388771 started by @NITISH-R-G

Summary by Sourcery

Improve activity log performance for large incident histories and prevent pull-request dashboard runs from targeting the deployment environment.

Enhancements:

• Virtualize the activity log history list so only visible saved incidents are rendered, improving loading performance for large histories.

CI:

• Avoid assigning the GitHub Pages deployment environment when the health dashboard workflow runs for pull requests.

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

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 741ad69b-6e77-45c0-8878-2efb5a5ced04

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[greptile-apps]

Your trial has ended. Reactivate Greptile to resume code reviews.

[github-actions]

Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information

[sourcery-ai]

Reviewer's Guide

Refactors SosActivityLogScreen to use a CustomScrollView with sliver-based layout so the activity history list is virtualized, avoiding O(N) rendering, while preserving existing UI structure and behavior for current session and history states.

File-Level Changes

Change	Details	Files
Refactor SosActivityLogScreen layout to use slivers and enable virtualization of the history list.	Replace top-level ListView with CustomScrollView composed of multiple SliverPadding sections. Move static header and current-session content into a SliverList with a SliverChildListDelegate so they remain non-virtualized. Convert the history.when() builder to return sliver widgets, including a SliverToBoxAdapter for the empty, loading, and error states. Render non-empty history items with a SliverList.builder so items are lazily built and virtualized, instead of constructing a Column of all cards.	lib/ui/sos_activity_log_screen.dart
Add an .orig backup of the previous SosActivityLogScreen implementation (likely generated tooling artifact).	Introduce sos_activity_log_screen.dart.orig containing a copy of the prior implementation for reference or tooling purposes.	lib/ui/sos_activity_log_screen.dart.orig
Minor pubspec.lock dependency resolution churn with no functional changes described.	Update dependency resolution entries in pubspec.lock with small version/metadata adjustments, likely from running pub get.	pubspec.lock

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[greptile-apps]

Your trial has ended. Reactivate Greptile to resume code reviews.

[github-actions]

Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information