row 254: README request-timeout sentence and a DEFERRED entry after the landing (#1759)

Doc-only commit after the row 254 landing. The library README now says
that a sync outlasting the server's 120-second hold gets request-timeout
and still finishes (Dewey N1, #1759 comment 30173; server.mjs sets the
120 s socket timeout and the broker promise runs on). DEFERRED records
Dewey N2: library-mapping-invalid, library-remote-invalid,
library-state-invalid and library-git still map to 502 until the Console
library routes row decides them. No test reads either file's content.

docs/plans/DEFERRED.md

@@ -346,6 +346,14 @@ at every gate. Started 2026-09-12 during the control board MVP.
   do nothing yet. The row that adds the Console library routes decides
   whether the tester listener gets `library.sync`. Duckworth's view is
   that it shouldn't, because sync is a human write. (2026-10-21)
+- **Console library routes: four library codes still map to 502.**
+  (Dewey N2 on the row 254 manifest, #1759 comment 30173.) Row 254
+  gave six library codes a STATUS entry in `packages/webui/src/bus.mjs`.
+  `library-mapping-invalid`, `library-remote-invalid`,
+  `library-state-invalid` and `library-git` still fall through
+  `busStatus` to 502. The row that adds the Console library routes
+  decides their statuses and gives its `humanCall` for `library.sync`
+  a timeout over 130 seconds. (2026-10-21)
 - **T27 sweep test leaves two `sleep 60` children running.**
   (Darkwing row 251 slot, darkwing-0113 and darkwing-0117; Dewey on
   r2, comment 30168.) The sweep test spawns two detached shells,

packages/library/README.md

@@ -168,7 +168,8 @@ with a `user`, once at start and then every 60 seconds; the slot is
 The human transport (`packages/bus/src/human-cli.mjs`) waits 130 seconds for `library.sync`, past the
 server's 120-second hold, and 5 seconds for every other verb. A client that gives up before the answer
 gets `outcome-unknown`, but the sync keeps running: a second call meanwhile gets `library-sync-busy`,
-and `library.status` shows the result once it ends. The Console has no library route yet: `cli.mjs`
+and `library.status` shows the result once it ends. A sync that outlasts the 120-second hold gets
+`request-timeout` from the server and still finishes the same way. The Console has no library route yet: `cli.mjs`
 passes `librarySync` to `startServer`, and `serve.mjs` doesn't read it.
 
 ## Tests