Changelog 0.2.9

Added

The x-axis now shows real calendar dates and times for time-stamped data.
New “Time Display” setting (Settings → Plot) to switch date/time axes between local time and UTC.
Importing a CSV/Excel file now shows a short preview where the x-axis column(s) can be confirmed or changed with a click – including whether the x-axis is time, so imported signals know their kind (e.g. “Y over Time”).
Synchronized cursor and range across plots: a single toggle links the cursor and range selection in every plot, so the cursor marks the same moment in time everywhere – whatever signals a plot holds.
On parametric / XY plots the synchronized cursor now shows the position at that moment as a marker, and a range highlights the covered part of the path. Points that fall outside the view glow at the edge, and markers show a label on hover.
Declare what a signal is recorded over in the properties panel: the panel now lists the X / Y / Z axes, and you can set what the x-axis represents (Time, Distance, Angle, Rotational speed, …). Signals built from it update to match.

CSV import now handles files with metadata lines above the column header (e.g. some device exports).
Date/time columns in CSV/Excel are now recognized as the time axis, whatever they are named.
CSV files with a units row below the header (e.g. s, km/h, Nm) are now imported correctly.
A CSV that cannot be read as a table now shows a clear message instead of a raw parser error.

CSV import is more tolerant of spaces after the delimiter (e.g. time, speed, rpm).
Changing a channel’s unit or x-axis kind can now be applied to several selected signals at once.
The onboarding tour now also walks through applying an operation to a signal and the Workflow panel.
AI reliability when driving ScryLab: naming an unknown tab when plotting now creates it (like plots), clearer guidance to split a measurement into sub-sources when comparing windows of one file, and no more dead-end references to commands the AI cannot call.
AI now keeps signals in matching x-axes: it won’t wrongly pair signals recorded over different things, and it can be told what a signal is recorded over without overwriting what you already set.