Run the formatter over the shard-naming change

`cargo fmt --all -- --check` is a CI gate and 9a51cc8 landed two files past
it, so the build has been red on master since regardless of what came after.
Whitespace only — a wrapped `Ok(...)` and two `assert_eq!`s split across
lines. No logic is touched and the tests are unchanged.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

ui/dr-ui/src/derived_sync.rs

@@ -404,8 +404,14 @@ mod tests {
 
     #[test]
     fn shard_names_round_trip() {
-        assert_eq!(shard_name("a1b2c3d4e5f6", 0), "shard-a1b2c3d4e5f6-0000.sqlite");
-        assert_eq!(shard_name("a1b2c3d4e5f6", 42), "shard-a1b2c3d4e5f6-0042.sqlite");
+        assert_eq!(
+            shard_name("a1b2c3d4e5f6", 0),
+            "shard-a1b2c3d4e5f6-0000.sqlite"
+        );
+        assert_eq!(
+            shard_name("a1b2c3d4e5f6", 42),
+            "shard-a1b2c3d4e5f6-0042.sqlite"
+        );
         assert_eq!(
             parse_shard(&shard_name("a1b2c3d4e5f6", 7)),
             Some(("a1b2c3d4e5f6", 7))