⚡ Bolt: optimize SosActivityLogScreen list virtualization

[NITISH-R-G]

💡 What:
Migrates the SosActivityLogScreen layout from a standard ListView that renders dynamic history items within a single synchronous Column over to a CustomScrollView leveraging SliverList.builder.

🎯 Why:
The previous implementation used items.map(...).toList() inside a Column which was then placed into a ListView. This approach completely bypasses Flutter's list virtualization mechanics. When viewing the SOS activity history, every single incident was being built, laid out, and painted immediately upon screen load, regardless of whether they were visible on screen. This creates a significant memory footprint and a potential frame drop (jank) spike on load, especially for users with a large history.

📊 Impact:

• Performance: Changes rendering complexity from O(n) (where n is the total number of history records) to O(1) (rendering only the few items actively visible on the screen).
• Memory: Significantly reduces memory allocations by lazily constructing widgets.
• Responsiveness: Noticeably faster screen initialization and smoother scrolling behaviour.

🔬 Measurement:
Run flutter test to verify rendering logic and routing remains correct. Navigate to the Activity Log screen on a physical device using the Flutter DevTools performance overlay to observe the reduction in initial build time/frame rendering time.

---

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

Summary by Sourcery

Optimize SosActivityLogScreen to use sliver-based scrolling for SOS activity history to improve performance and memory usage.

Enhancements:

• Replace ListView with CustomScrollView and sliver-based layout for the SOS activity log screen.
• Virtualize SOS incident history items using SliverList.builder instead of eagerly building all items in a Column.

[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: 553ac22d-4543-4170-8d0e-e9b29d70bd67

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

Migrates SosActivityLogScreen from a non-virtualized ListView/Column layout to a sliver-based CustomScrollView with virtualized SliverList, preserving existing UI semantics while improving performance and memory usage.

File-Level Changes

Change	Details	Files
Replace the ListView + Column-based SOS activity log layout with a CustomScrollView using slivers for proper list virtualization.	Wrap the screen body in CustomScrollView instead of ListView. Introduce top SliverPadding with SliverChildListDelegate for static header, current session, and section title content. Introduce bottom SliverPadding containing the history AsyncValue rendered as slivers, including saved incidents list or empty-state text.	lib/ui/sos_activity_log_screen.dart
Virtualize the incident history list using SliverList.builder and adapt loading/error states to sliver-compatible widgets.	Replace Column + items.map(...) history rendering with SliverList.builder that lazily builds _historyCard for each item. Handle empty history with SliverToBoxAdapter containing the informational Text message. Convert loading and error UI from regular widgets to SliverToBoxAdapter children to integrate into CustomScrollView.	lib/ui/sos_activity_log_screen.dart
Update dependency lockfile to reflect the current Flutter/Dart package state associated with this change.	Regenerate pubspec.lock as part of the build/tooling process.	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