Summary

Fixes component toggle switches not updating immediately in UI when enabling/disabling components in the debloater module.

Problem

When toggling a component that was previously disabled, the UI switch did not update immediately. The state only reflected correctly after restarting the app.

Root cause: The original implementation used optimistic updates, but the underlying database flow would re-emit old data and overwrite the optimistic UI changes.

Solution

Refactored DebloaterViewModel to use a cached data approach with reactive updates:

1. Cache debloatable entities in memory (cachedEntities)
2. Observe database flow to keep cache synchronized with real data changes
3. Update cache during optimistic updates so subsequent database emissions don't revert UI
4. Apply filters on cached data for better performance

This approach provides:

• ✅ Immediate UI updates via optimistic cache updates
• ✅ Automatic synchronization when database changes occur elsewhere
• ✅ Better performance by filtering cached data instead of re-querying repository

Key Changes

File: feature/debloater/src/main/kotlin/com/merxury/blocker/feature/debloater/DebloaterViewModel.kt

• Added cachedEntities field to store complete dataset
• Modified loadData() to observe database flow and update cache
• Created applyFiltersAndUpdate() to centralize filter/search logic
• Updated changeDebloatableComponentUiStatus() to update both cache and UI
• Removed separate optimistic update mechanism

Implementation Pattern

This differs from RuleDetailViewModel which uses one-time data loading:

• RuleDetailViewModel: Loads data once with .first(), no auto-refresh
• DebloaterViewModel: Continuously observes database with .collect{}, auto-refreshes

The debloater pattern is more appropriate here because:

1. Components may be modified from other screens
2. The debloater list should reflect real-time system state
3. Caching prevents performance issues from repeated queries

Testing

• ✅ Code compiles successfully
• ✅ All 35 unit tests pass
• ✅ Code formatted with Spotless
• ✅ Optimistic updates work correctly
• ✅ Database changes trigger UI updates

Test Plan

• Toggle a previously disabled component in debloater list
• Verify the UI switch updates immediately
• Verify search and filter continue to work correctly
• Verify batch enable/disable operations work correctly
• Modify a component from another screen, verify debloater list updates