The automatic data refreshing mechanism has been updated to handle asynchronous state changes more reliably. It now incorporates checks to determine if the active repository path has changed during background operations. This prevents stale or incorrect data from being displayed if a user navigates away from or switches repositories while a refresh cycle is in progress.
- Added path validation checks after status fetching and bundle opening
- Ensured all subsequent refresh calls use the validated current repository path