diff --git a/docs/FILTERING.md b/docs/FILTERING.md
index dc7ccd9e..889256cf 100644
--- a/docs/FILTERING.md
+++ b/docs/FILTERING.md
@@ -173,7 +173,7 @@ independent target resolver. Presentation source precedence is:
 below. The resolver still retains source metadata for preview diagnostics, but
 the rendered marker always uses its base icon on a neutral dark plate: no state
 morph, work/open/alarm/unavailable paint, activity, RGB, value or satellite
-temperature/humidity/LQI badge. Live vacuum puck/trail/room-highlight overlays
+temperature/humidity/LQI badge. The live vacuum puck, trail and route warning
 are also suppressed. This changes presentation only: hover/focus, service-call
 feedback, controls, Glow and room light aggregation keep using the real device.
 Hidden, removed or HA-disabled lifecycle rules still outrank display mode.
diff --git a/docs/USER-GUIDE.ru.md b/docs/USER-GUIDE.ru.md
index 96ffbdb4..470504b0 100644
--- a/docs/USER-GUIDE.ru.md
+++ b/docs/USER-GUIDE.ru.md
@@ -1339,7 +1339,7 @@ Hover включается только после события от наст
 «Всегда статичный значок» — осознанное исключение из общей матрицы состояний.
 Маркер не меняет подложку или иконку, не показывает тревогу, недоступность,
 RGB-цвет, значение, температуру, влажность и LQI. Для пылесоса также скрываются
-живой puck, след и подсветка убираемой комнаты, но сохранённая история не
+живой puck, след и предупреждение о маршруте, но сохранённая история не
 удаляется. Hover/focus остаются такими же, как у других маркеров; клик, controls,
 Glow и заливка «Свет» продолжают работать по фактическому состоянию и отдельным
 настройкам устройства. Для привязок, способных сообщать о тревоге, редактор
diff --git a/docs/VACUUM.md b/docs/VACUUM.md
index 43335ef4..35a6c03b 100644
--- a/docs/VACUUM.md
+++ b/docs/VACUUM.md
@@ -66,9 +66,8 @@ hint; arbitrary unselected cameras do not.
 ## Maps and floors (#162)
 
 One robot can hold several maps, and each map belongs to one space. The dock
-marker never moves: it stays in `marker.space`, while the live puck, the
-current trail and the room highlight belong to the space of the map that is
-active right now.
+marker never moves: it stays in `marker.space`, while the live puck and the
+current trail belong to the space of the map that is active right now.
 
 A **route** is one saved answer to "this exact map of this exact source lives
 here": `{ id, source, map_id, space, calibration }`. The exact source is part
@@ -196,10 +195,15 @@ marker.vacuum = {
   live?, trail?, trail_mode?, source?,
   calibration?: { [map_id]: [a,b,c,d,e,f] },   // legacy-read after #162
   map_routes?: [{ id, source, map_id, space, calibration? }],
-  room_highlight?, segment_map?
+  room_highlight?, segment_map?    // schema only: no runtime consumer (#12)
 }
 ```
 
+`room_highlight` and `segment_map` are accepted and round-tripped so that plans
+written by any version stay readable, but nothing draws them: the room-cleaning
+highlight (#12) was rejected, not shipped. A live vacuum draws its puck, its
+trail and — on an unmapped map — the route warning; that is the whole overlay.
+
 All fields are optional and old plans remain readable. When `map_routes` is
 absent or `null`, every valid `calibration[map_id]` is read as an effective
 route into the dock's space, so a plan made before #162 renders byte for byte