⚡ Bolt: [performance improvement] Replace ListView with CustomScrollView for log virtualization

[NITISH-R-G]

💡 What: Replaced the standard ListView and nested Column in SosActivityLogScreen with a CustomScrollView and SliverList.builder. Also ensured Riverpod's AsyncValue data states properly yield Sliver-compatible widgets.
🎯 Why: Rendering a potentially unbounded list (the SOS activity history) inside a Column nested within a ListView breaks Flutter's list virtualization. This forces the framework to synchronously build every history item when the screen opens, resulting in O(n) layout and paint times. By transitioning to Slivers, Flutter now only builds the widgets lazily as they scroll into view (O(1) active rendering).
📊 Impact: Reduces time to first frame (TTFF) when opening the log screen for users with extensive SOS histories and scales safely without causing jank or memory spikes.
🔬 Measurement: Verified that the UI identical. Run the app, populate several mock SOS incidents, and scroll through the log screen. DevTools Timeline will show fewer widget builds in the initial render frame.

---

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

Summary by Sourcery

Improve the SOS activity log’s rendering performance and keep pull request dashboard workflows from configuring production deployment environments.

Enhancements:

• Virtualize SOS activity history rendering with sliver-based scrolling to improve initial load performance and scalability for large histories.

CI:

• Prevent pull request workflow runs from targeting the GitHub Pages deployment environment.

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

[greptile-apps]

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

[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: 94a69e6f-bc53-4353-b668-09788e47d3eb

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

[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 + SliverList-based layout instead of a ListView with a nested Column, enabling proper list virtualization and making the Riverpod AsyncValue branches return sliver-friendly widgets.

Flow diagram for SosActivityLogScreen scrollable layout refactor

flowchart TD
  subgraph SosActivityLogScreen_body[CustomScrollView layout]
    CS[CustomScrollView]
    CS --> SP1[SliverPadding top]
    SP1 --> SL_static[SliverList staticContent]

    CS --> SP2[SliverPadding bottom]
    SP2 --> AV_history[AsyncValue history.when]

    subgraph AsyncValue_history_branches[history.when branches]
      AV_history -->|data items isEmpty| SBA_empty[SliverToBoxAdapter emptyText]
      AV_history -->|data items nonEmpty| SL_history[SliverList.builder historyCards]
      AV_history -->|loading| SBA_loading[SliverToBoxAdapter CircularProgressIndicator]
      AV_history -->|error| SBA_error[SliverToBoxAdapter errorText]
    end
  end

Loading

File-Level Changes

Change	Details	Files
Replace ListView/Column layout with a CustomScrollView and top SliverList for static header and current-session content while preserving existing UI structure and padding.	Swap the ListView body for a CustomScrollView with slivers to host the entire screen content. Wrap the static banner, optional current-session section, and section title widgets in a SliverPadding containing a SliverList with a SliverChildListDelegate. Adjust padding so the top section uses top padding only, leaving bottom padding to the history section below.	lib/ui/sos_activity_log_screen.dart
Convert Riverpod AsyncValue-driven history content into sliver-compatible widgets with lazy item building for the activity list.	Wrap the history.when(...) result in a SliverPadding to control horizontal and bottom spacing. Change the data branch from building a Column of all history cards to returning a SliverList.builder that lazily builds each history item. Update the empty, loading, and error states to return SliverToBoxAdapter wrappers so they can be composed inside CustomScrollView slivers.	lib/ui/sos_activity_log_screen.dart

---

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