Releases ·
Roastwarden 0.31.1
Charts read time as a clock (2:00, 4:00, not 1:40 and 3:20), and a roast's chart in History fits a phone the way the Roast page's does. Research on an agent inside the app concluded against a chat in the dashboard.
Changed
- Chart times read as a clock: the Roast page's chart, a roast in History, roasts compared and the site's "Watch a roast" mark time in steps of 1, 2, 3 or 5 minutes (2:00, 4:00) instead of 1:40 and 3:20.
- A roast's chart in History on a phone is laid out like the Roast page's: narrower axes, units as the axis names, no separate heater/fan % axis (hover reads them), so the curves get most of the width.
Fixed
- The telemetry WebSocket's Node example (
websocket-v2.md) sends the API token on the upgrade request; without it a server that needs a login for reads refused it.
Docs
- Research for an agent inside the app (ROADMAP Next 81,
docs/research/in-app-agent-2026-11-04.md): no chat in the dashboard; chat apps would connect to Roastwarden over MCP with an ordinary token, kept for when a user asks. prediction.md's design notes set the live RoR warnings' limits beside the roast notes' (a stall warns at 1 °C/min, the note calls one at 0.5).