extend telemetry queue to five seconds

docs/binary-record-v1.md

@@ -75,7 +75,7 @@ before that first valid frame separately from CRC failures after synchronization
 ## Buffering
 
 Acquisition runs in a dedicated higher-priority task and writes complete samples
-to a 128-entry RAM queue. The lower-priority output task batches up to eight
-records per frame. At 100 Hz this queue represents about 1.28 seconds of
+to a 512-entry RAM queue. The lower-priority output task batches up to eight
+records per frame. At 100 Hz this queue represents about 5.12 seconds of
 decoupling from a blocked transport. Queue overflow never overwrites an older
 sample silently: sequence gaps and the cumulative lost-sample counter expose it.

docs/binary-transport-validation-2026-08-17.md

@@ -51,7 +51,7 @@ BLE link overhead, far below the previous CSV stream.
 ## Task separation and buffer
 
 The 100 Hz I2C acquisition runs at FreeRTOS priority 10. USB encoding/output runs
-at priority 5 and receives samples through a 128-entry queue (about 1.28 seconds
+at priority 5 and receives samples through a 512-entry queue (about 5.12 seconds
 at 100 Hz). The hardware capture's zero timing anomalies and zero loop overruns
 confirm that packet encoding, CRC, float metadata, and USB output did not disturb
 the acquisition cadence.