The run timeline: your QA's story, drawn

Post 24 gave the traces to your agent. Now they get a face: the run timeline turns the same structured feed into a picture — one lane per QA, virtual time on the x-axis, every event a colored mark. Multi-QA interactions stop being JSON archaeology.

Enable the trace categories and start the viewer; the timeline lives at /timeline (linked from the viewer header):

-- .flua-directives
--%%trace:api,ui,net,timer
--%%syslog:run.json

.venv/bin/flua --ui 8091 qa.lua
# flua: UI viewer on http://127.0.0.1:8091/ — open it in a browser
open http://127.0.0.1:8091/timeline

What you see:

• One lane per QA — plus a system lane for run lifecycle — with timers in their own lane (<tag> · timers), because timer starts/expiries would drown everything else.
• Colors by kind — blue api calls, green ui events, orange net operations, purple timer, gray lifecycle.
• Hover for everything — time, QA, event name, detail, and the full data JSON. Events stacked at the same instant list together, so nothing hides behind its neighbor.
• Time stays honest — a fixed minimum scale (40px per virtual second): long runs grow past the page width and the timeline scrolls, instead of compressing into unreadability. The clear button drops the drawn history but keeps the scale.

Because the x-axis is virtual time, the timeline plays perfectly with time travel: run with --speed 60 and watch a minute of behavior compress into a second, or --instant to have the whole run draw itself at once. Add --%%syslog:run.json (as above) and the same events persist for post-mortems — the live view reads the recent 2000 from the in-memory feed.

Next time: proxy mode — flua mirrors a QA onto your real HC3, so it runs offline but behaves as a device on the controller. The deepest offline-online blend yet.

timeline: /timeline under --ui · traces: USAGE.md · pip: fibaro-flua 0.1.84 · flua: https://github.com/jangabrielsson/flua