fix(fuse): do not take a new file Drive lists before its commit as empty (B163)

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: B127 and B141 to B162.
+- Fixes from the simulation and account runs since then: B127 and B141 to B163.
 - **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`.
 
@@ -97,7 +97,10 @@ Tracks `docs/MILESTONE-3.0.0.md`. Update it with every commit that moves a phase
          to reach Drive at once and now accepts queued ones. The move cases were the harness:
          it retried every source after one was busy, and expected a refusal where a mirror to
          mirror move carries the local copy along. The journal showed a conflict copy retrying
-         into a deleted folder (B150, fixed). Not confirmed yet.
+         into a deleted folder (B150, fixed). Not confirmed yet. The run on 2.10.0
+         (2026-10-04: 260 passed, 3 failed) failed a new file that read back empty (B163,
+         fixed), a 128-entry folder that listed 129, and its cleanup, which ran while the
+         daemon was restarting.
 5. **Release**: 2.10.0 is tagged; the 2.9.0 tag still waits for the user's go-ahead.
 
 ## After 3.0.0