fix(fbuild-deploy): repair broken intra-doc links and fmt drift (#201)

- esp32_native.rs module-level `//!` docs use `crate::esp32::...`
  instead of `super::esp32::...`. Rustdoc does not resolve `super`
  from inner doc comments at the module file level under rustc 1.94.1,
  which broke `cargo doc --workspace --no-deps` with
  `RUSTDOCFLAGS=-D warnings`. Also fully qualify `VerifyOutcome` as
  `crate::esp32::VerifyOutcome` since it is not in scope at the
  module-doc resolution site.
- esp32.rs: apply `cargo fmt` — the native-write early-return block
  had drifted out of the canonical layout.

Fixes CI runs 24900888165 (Documentation) and 24900888192 (Formatting).

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: zackees

crates/fbuild-deploy/src/esp32.rs

@@ -1245,11 +1245,9 @@ impl Deployer for Esp32Deployer {
 
         #[cfg(feature = "espflash-native")]
         if self.use_native_write {
-            if let Some(result) =
-                native_write_or_fallback(port, "write-flash", || {
-                    self.try_deploy_native(firmware_path, port)
-                })
-            {
+            if let Some(result) = native_write_or_fallback(port, "write-flash", || {
+                self.try_deploy_native(firmware_path, port)
+            }) {
                 return Ok(result);
             }
         }

crates/fbuild-deploy/src/esp32_native.rs

@@ -1,6 +1,6 @@
 //! Native ESP32 `verify-flash` **and** `write-flash` implementations
 //! backed by the [`espflash`] crate. Alternatives to the default
-//! [`super::esp32::Esp32Deployer`] path, which shells out to Python
+//! [`crate::esp32::Esp32Deployer`] path, which shells out to Python
 //! `esptool`.
 //!
 //! # Why (issue #66)
@@ -16,7 +16,8 @@
 //! # Scope
 //!
 //! * `verify-flash` — three regions (bootloader / partitions /
-//!   firmware), same [`VerifyOutcome`] semantics as the esptool path.
+//!   firmware), same [`crate::esp32::VerifyOutcome`] semantics as the
+//!   esptool path.
 //! * `write-flash` — same three regions, same
 //!   [`DeploymentResult`]/[`DeployOutcome`] shape as the esptool path.
 //!   Progress callbacks from espflash are bridged into `tracing` so the
@@ -36,9 +37,9 @@
 //! # Opt-in
 //!
 //! `verify-flash` is guarded by
-//! [`super::esp32::Esp32Deployer::with_native_verify`] (daemon env:
+//! [`crate::esp32::Esp32Deployer::with_native_verify`] (daemon env:
 //! `FBUILD_USE_ESPFLASH_VERIFY`), and `write-flash` by
-//! [`super::esp32::Esp32Deployer::with_native_write`] (daemon env:
+//! [`crate::esp32::Esp32Deployer::with_native_write`] (daemon env:
 //! `FBUILD_USE_ESPFLASH_WRITE`). The two flags are independent —
 //! users can flip one without the other while the native write path
 //! accumulates bench time on every ESP32 family member.