chore: remove daemon roadmap — project is complete

All phases shipped: daemon, gRPC API, Python client, GEM300 support,
operations hardening. The roadmap served its purpose; replace it with
final state documented in README + docs/*.md chapters.

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>

README.md

@@ -53,7 +53,7 @@ Three ways in, same engine underneath:
    its function name; `eq.names.event.*` / `.alarm.*` / `.command.*` are
    autocomplete-able, typo-checked views fetched from the live daemon — so
    you rarely type a bare string. (The plain forms — `@eq.on("START")`,
-   `eq.fire("ProcessStarted")` — still work.)
+   `eq.fire("ProcessStarted")` — also work.)
 
    A complete tool is ~25 lines: [clients/python/examples/mini_tool.py](clients/python/examples/mini_tool.py).
 
@@ -69,9 +69,6 @@ Three ways in, same engine underneath:
    for all of GEM), and wire behaviour with `commands.set_handler`.
    `apps/secs_server.cpp` is the ~110-line canonical example.
 
-Status and remaining work for the daemon/client track:
-[docs/DAEMON_ROADMAP.md](docs/DAEMON_ROADMAP.md).
-
 ---
 
 ## Documentation map