M4a tasks 14 and 15: glue written, calls tabled, after task 14's session wrote nothing

Task 14's session read the crate to learn the APIs and planned `connect` in prose until it was
cut off. `connect`, `Gateway::new` and `catch_up` are now written; the task lists every call with
its signature and makes the copy and the failing test the first actions. Task 15's comment is
rewritten one step per item. Both checked to fail, then pass when filled from their comments.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

docs/plans/M4a/README.md

@@ -78,6 +78,18 @@ At the end of task 15: about 762 tests (650 before task 01).
   skeletons were checked in a scratch copy of the branch: they compile and fail their tests, and
   filled literally from their comments they pass (7 of 7, 10 of 10 five times), clippy clean, gate
   ok. Resume from task 08.
+- 2026-09-23, task 14: tasks 08 to 13 committed, each on its first session. Task 14's session
+  wrote nothing, not even the copies: it read twenty source files to learn the APIs, then planned
+  `connect`'s wait for `hello` in prose ("let me stop designing", and it did not) until it was cut
+  off. Twelve-plus `todo!()`s across two files and the whole crate's API were too much for one
+  turn. The design model wrote `connect`, `Gateway::new` and `catch_up` as glue (leaving
+  `catch_up_channel`), gave `handle_post` and `start` their borrow- and move-sensitive lines
+  verbatim, added a table of every call the helpers make with its signature (checked against the
+  branch), and made copying and seeing the tests fail the first two actions. Task 15's `serve`
+  comment, whose numbered steps had run together, was rewritten one step per item. Both were
+  checked in a scratch copy of the branch at task 14's start: the skeletons compile and fail
+  (`serve` 6, `serve_restart` 5 with 2 passing, `main` 4 with 1 passing), and filled from their
+  comments they pass (five runs), clippy clean, gate ok. Resume from task 14.
 
 ## Running it