Enforce a single daemon per geth home

docs/roadmap.md

@@ -17,6 +17,15 @@ For deployment-readiness work that cuts across feature areas, see
 
 ## Operator Usability
 
+- `[x]` Enforce one daemon per geth home.
+  Acceptance criteria:
+  - `[x]` Daemon startup claims the local control endpoint before starting
+    network and background modules.
+  - `[x]` A live endpoint rejects another daemon with the stable
+    `daemon_already_running` code instead of unlinking the first socket.
+  - `[x]` Stale, unreachable socket paths are recovered automatically.
+  - `[x]` Tests cover stale recovery and live second-daemon rejection.
+
 - `[x]` Make startup modes and the daemon lifecycle discoverable.
   Acceptance criteria:
   - `[x]` Base and nested CLI help explain every command family instead of