fix(core): a folder listed just as its create lands is listed from the database (B177)

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 B176.
+- Fixes from the simulation and account runs since then: B127 and B141 to B177.
 - **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`.
 
@@ -121,6 +121,8 @@ Tracks `docs/MILESTONE-3.0.0.md`. Update it with every commit that moves a phase
          in the same gap was refused with `EACCES` (B174, fixed). The loop on 378667f failed
          seed 8: a file replaced by a rename in that gap stayed on Drive (B175, fixed), and
          seed 12: a write closed as its file's create landed was dropped (B176, fixed).
+         The account run on 378667f: a folder listed as its create landed asked Drive by
+         its stand-in and answered `EIO` (B177, fixed).
 5. **Release**: 2.10.0 is tagged; the 2.9.0 tag still waits for the user's go-ahead.
 
 ## After 3.0.0