docs(agent): update SCADA protocol docs

docs/agent-ui-protocol.md

@@ -80,26 +80,13 @@ fall back to `fallbackText`.
 Initial mappings:
 
 - `show_chart` -> `chart`
-- `locate_features` -> `map_action`
 - `zoom_to_map` -> `map_action`
-- `render_junctions` -> `map_action`
-- `apply_layer_style` -> `map_action`
-- `view_history` -> `registered_component: HistoryPanel`
 - `view_scada` -> `registered_component: ScadaPanel`
 
-`view_history` parameters must include `start_time` and `end_time` ISO8601
-timestamps with `start_time < end_time`. When the Agent needs historical
-monitoring values for analysis or a chart, it should call
-`query_monitoring_readings` first, then use `view_history` only to open the
+When the Agent needs historical SCADA values for a chart or explanation, it
+should call `query_scada_readings` first, then use `view_scada` only to open the
 frontend panel.
 
-`render_junctions` accepts only a `render_ref`. The frontend must resolve the
-full payload through:
-
-```text
-GET /api/v1/agent/chat/render-ref/:render_ref?session_id=:session_id
-```
-
 ## State Persistence
 
 Assistant messages may contain: