Add source-aware UART log replay

README.md

@@ -66,6 +66,19 @@ corrected series; legacy input without a source keeps the previous behavior.
 Synthetic `source=trajectory` points form a third independent green ground-truth
 path. The map legend identifies all three series.
 
+## UART log replay
+
+Use the `UART Replay` button (or `Dosya > UART Log Replay...`) to feed a recorded
+UART `.log`/`.txt` file back through the same parser used by the live serial port.
+Choose the raw GPS update interval (default `200 ms`) and sensor/fused update
+interval (default `50 ms`) in the replay dialog. Press `Replay Durdur` to stop.
+
+Recorder timestamps are optional and do not control replay speed. The replayer
+removes a leading timestamp when present, identifies `source=gps` as raw GPS and
+`source=imu_corrected` or `[FUSION]` as fused/sensor output, then synthesizes the
+two update timelines while retaining the original UART line order. Other UART
+diagnostic lines are forwarded with the surrounding location update.
+
 ## Sentetik ESKF senaryolarini açma
 
 GPS deposundan 48 kombinasyonun replay loglarini üretin:
@@ -263,5 +276,8 @@ without logging out.
 - UART log and telemetry views are refreshed in batches so a high-rate serial stream does not
   rebuild the complete interface for every received line. The locations table uses a virtual
   model and remains usable with a high `Max` value.
+- Her basarili UART baglantisi, dosya adinda ve her satirda yerel zaman damgasi bulunan ayri bir
+  log olusturur. Dosyalar kaynak kodun ana klasorundeki `uart_logs` dizinine yazilir;
+  `LOCATION_PLOTTER_UART_LOG_DIR` ile farkli bir klasor secilebilir.
 - If no new plotted location arrives for 10 seconds while listening, current location
   points and analysis values are cleared.