chore: repoint exfat-fs patch to the v0.1.3-tag-based fix commit

The exfat-fs empty-file fix branch was rebuilt on top of the upstream v0.1.3
release tag (instead of an orphan commit) so it has proper shared history and
reads as a clean "1 commit ahead of v0.1.3". Update the pinned rev accordingly;
tree and behavior are identical (v0.1.3 + the one-function fix).

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

Cargo.lock

@@ -481,7 +481,7 @@ dependencies = [
 [[package]]
 name = "exfat-fs"
 version = "0.1.3"
-source = "git+https://github.com/jujuforce/exfat-fs.git?rev=7067f6afe3c21d9c737288475b29e5dae790e206#7067f6afe3c21d9c737288475b29e5dae790e206"
+source = "git+https://github.com/jujuforce/exfat-fs.git?rev=dc50d0539246a91f08ad01b565e408f7f94136b6#dc50d0539246a91f08ad01b565e408f7f94136b6"
 dependencies = [
  "bitflags",
  "bytemuck",

Cargo.toml

@@ -27,7 +27,7 @@ strip = "none"
 # empty file legitimately has FirstCluster = 0 / DataLength = 0. That aborts
 # the whole extraction the moment an OPTION container contains any 0-byte file.
 # Until the fix lands in a published release, override with a fork branch that
-# is the 0.1.3 release plus only that one-function fix (identical public API).
+# is the v0.1.3 release tag plus only that one-function fix (identical public API).
 # See https://github.com/jujuforce/exfat-fs/tree/v0.1.3-empty-file-fix
 [patch.crates-io]
-exfat-fs = { git = "https://github.com/jujuforce/exfat-fs.git", rev = "7067f6afe3c21d9c737288475b29e5dae790e206" }
+exfat-fs = { git = "https://github.com/jujuforce/exfat-fs.git", rev = "dc50d0539246a91f08ad01b565e408f7f94136b6" }