fix: skip needless remote connects in local read paths

The new resolve_remote_latest function returns a tuple of three values: (Option<Hash>, bool, bool). In the status function, the third value is destructured into remote_available, but it is never used. The original code used repository.remote().await.is_ok() to determine availability, but now remote_available is computed and ignored. This suggests either a logic error where the new availability flag should replace the old check, or dead code that should be removed.