Clarify unavailable telemetry before recording

Clarify the empty viewer message: a recording enables measured position and speed, while controls and sensors remain unrecorded. Update the corresponding frontend identity and release hashes with this wording change.

Hosted verification of the recorded-drive viewer from PR #5 succeeded on Replica A01 Beginner with a Formula starter: the 5-second request returned 51 native samples and the 15-second request returned 151. The first measured pose was (4608, 2688), with 0.0 km/h and 0 contacts. The two recordings displayed the same tick-300 position, speed and contacts. Playback reached tick 300 and remained finished; scrubbing the long recording reached tick 900. No training job or GPU allocation was started.

track-map.js

@@ -291,7 +291,7 @@
       if(!recording){
         setText('replay_status',reason||(hasRunSummary?summaryOnly:noRecording));
         setText('replay_time_label','No recorded samples');
-        setText('replay_readout','Position, speed, controls and sensors are unavailable until a replay is recorded.');
+        setText('replay_readout','Record a drive to inspect position and speed. Controls and sensors are not recorded.');
       }else{
         const state=cursor>=last?'Finished. Use Restart to view it again.':playing?'Playing.':'Paused.';
         setText('replay_status',`Fresh recorded CPU evaluation · ${recording.frames.length} samples · 60 Hz physics and controls · 10 Hz recording. ${state}`);