docs: mark daemon/client plan as implemented

docs/daemon-client-plan.md

@@ -1,6 +1,13 @@
 # patterm: persistent daemon + thin networked client — implementation plan
 
-Status: proposed (for peer review). Branch: `feat/daemon-client-split`.
+Status: implemented — Phases 0–4 landed on this branch. Branch: `feat/daemon-client-split`.
+
+> Implemented: pty workdir/process-group + protocol/Transport/loopback foundation;
+> multi-project `ProjectRegistry`; out-of-process unix-socket daemon with auto-start,
+> `daemon stop`/`ls`, detach (Ctrl-]) + reconnect; opt-in LAN TCP listener with a
+> lightweight bearer token + `patterm connect`; per-pane display-owner sizing for
+> multi-client viewing. Deferred (not built): TLS (transport kept pluggable),
+> remote MCP, durable restore of live PTYs across daemon restart.
 
 ## Goal