fix(fuse): changes that failed on a short outage go out once the link is back (B189)

docs/BUGS.md

@@ -12,6 +12,25 @@ Conventions:
 
 ---
 
+## B189 — A change that failed on a short outage waits out its retry long after the link is back
+
+**Status:** Fixed (unverified).
+**Found:** 2026-10-05, in the confirmation run on 2baad67 (`three_clients_one_writer_each`
+seed 6, every replay). A client's link was down for 0.3 s, during which it made a folder and a
+file. Their uploads failed once, and 4 s after the link came back they were still queued.
+
+**Where:** the failure path of `Core::run_pending_drain` in `crates/pdfs-fuse/src/drain.rs`.
+
+**Cause.** Every syscall and the event poll take the mount offline when Drive does not answer,
+and the probe that brings it back makes every backed-off op due at once. The drain was the one
+caller that did not. An outage that only the drain met left the mount online, so nothing probed
+for the link's return, and the ops sat out a backoff that doubles with each failure, up to five
+minutes.
+
+**Fix.** A drain attempt that cannot reach Drive takes the mount offline like any other call.
+Test `a_write_that_failed_on_a_short_outage_goes_out_soon_after_the_link_returns` in
+`crates/pdfs-fuse/src/sim/daemon.rs`.
+
 ## B188 — A restart can leave a queued write retrying forever on a file deleted while open
 
 **Status:** Fixed (unverified).

docs/CHANGELOG.md

@@ -111,6 +111,8 @@ by its local id, in the queue, the stored tree and pins alike.
   A write into it no longer failed with "Input/output error" (B186).
 - **An uploaded file no longer leaves a copy of itself in the cache** until the next start
   (B187).
+- **Changes that failed during a short outage go out soon after the connection is back**, not
+  after a retry delay of up to five minutes (B189).
 - **A file renamed just as its upload finished keeps its new name.** The mount no longer showed
   the old name, and a second rename no longer failed with "No such file or directory" (B152,
   B172).

docs/MILESTONE-3.0.0-STATUS.md

@@ -9,7 +9,7 @@ Tracks `docs/MILESTONE-3.0.0.md`. Update it with every commit that moves a phase
 - **Phase 2**: local ids, inode = local id, one tree for every mount (2.10.0).
 - **Phase 3, first part**: mkdir, create, rename, unlink and rmdir on the mount are recorded
   locally and sent from the queue; `"local_first": false` brings back the old path (5e0f30c).
-- Fixes from the simulation and account runs since then: B125, B127, B130 and B141 to B188.
+- Fixes from the simulation and account runs since then: B125, B127, B130 and B141 to B189.
 - **Sync issues, first cut** (§6.2): refusals sorted into issues, shown at once in the app,
   tray and CLI; Export button and `pdfs sync export`; `pdfs sync issues`; Discard button and
   `pdfs sync discard`; a warning badge on the node in the file browser.
@@ -114,7 +114,8 @@ Tracks `docs/MILESTONE-3.0.0.md`. Update it with every commit that moves a phase
          a retry after a write replaced its blob (B185, fixed), and a file deleted offline
          while open that lost the bytes its handle read (B186, fixed; older than 3.0.0).
          The run on 2baad67 found that a restart before such a file's trash went out queued
-         its kept bytes again, for good (B188, fixed).
+         its kept bytes again, for good (B188, fixed), and changes that sat out their retry
+         after an outage only the drain had met (B189, fixed; older than 3.0.0).
    - [ ] A clean account run. The one on a6f36d5 (2026-10-04, LAN: 427 passed, 12 failed)
          failed B113 and B121 on every on-demand mount, two mirror-to-mirror move cases, and
          the journal check. B121 was a bug (B149, fixed); B113's case still expected creates