docs(ops): document ActiveSync operations monitor

README.md

@@ -19,6 +19,7 @@ The documentation is split by audience:
 | You are… | You want to… | Read |
 |----------|--------------|------|
 | **Administrator / end user** | Enable ActiveSync, configure protocol versions, streaming, logging, the web server endpoint, and per-user policy | [`doc/configuration.md`](doc/configuration.md) |
+| **Administrator / operator** | Monitor device health, triage live problems, and use the CLI and admin workflows | [`doc/ops-monitor.md`](doc/ops-monitor.md) |
 | **Library user / integrator** | Embed the library in your own product: server object, driver API, state backends, custom backends | [`doc/integration.md`](doc/integration.md) |
 | **ActiveSync developer** | Understand the internals: components, request lifecycle, Sync anatomy, state machine, tests | [`doc/architecture.md`](doc/architecture.md) |
 

doc/todo.md

@@ -34,15 +34,13 @@ FRAMEWORK_6_0 / 3.x line.
   Outlook weekly-series traffic. Documented in `doc/protocol-versions.md`
   (Tasks section).
 
-## Operations and monitoring (out of library scope)
+## Operations and monitoring (implemented across packages)
 
-- **EAS usage dashboard / “top-like” monitor**
-
-  A live view of active devices, error rates, and stuck sync keys would be
-  valuable for operators but belongs in a separate admin tool or Horde UI
-  module, not in the protocol library. Per-device protocol logging
-  (`logging.type = perdevice` in Horde config) is the supported debugging
-  path today.
+The shared, storage-independent health evaluator and DTOs live in this
+library. The fleet snapshot service lives in `horde/core`; the
+`horde-activesync` CLI and ActiveSync Administration page live in
+`horde/horde` (the `horde/base` repository). See
+[`ops-monitor.md`](ops-monitor.md) for the health model and operator cookbook.
 
 ## Horde 6 / FRAMEWORK_6_1 (breaking changes — planned refactor)