Small changes. Better testing.

Running tofupilot deploy on a station required a user login, which previously overwrote the station's own credentials and stopped its service from starting.

• Fixed user and station logins so they no longer overwrite each other; a station stays authenticated after you log in as a user to deploy.
• Improved the station service so it keeps running after a user login on the same machine.
• Updated existing stations to migrate automatically on upgrade, with no re-login required.

Headless test jigs that run as root could no longer open the kiosk operator UI, leaving runs stuck on unit identification.

• Fixed the kiosk operator UI failing to start for foreground run --kiosk on root stations.
• Restored remote viewing of the kiosk over an SSH port-forward on headless machines.
• Kept the root station service hardened: its command channel still refuses to bind as root.

A connection drop during the binary download — common after a network switch or wake-from-sleep — could abort tofupilot update partway through, even when the server was healthy.

• Fixed tofupilot update failing when the connection dropped mid-download
• Added automatic retries with backoff so an interrupted transfer restarts cleanly instead of aborting the update

A transient connection drop right after a network switch or wake-from-sleep could abort tofupilot update even when the server was healthy, and an immediate re-run would succeed.

• Fixed tofupilot update failing on a single transient network error when checking for the latest version
• Added automatic retries with backoff so a brief connection hiccup no longer interrupts the update

Attachments produced during a CLI run now upload reliably and display correctly on the dashboard.

• Fixed attach.data attachments being silently dropped on native test runs so they never reached the dashboard.
• Fixed attach.file attachments uploading without a size, type, or image preview.
• Improved cleanup so attachment files left by a failed or aborted run no longer pile up on disk.

Guide and template pages were briefly returning an error instead of loading.

• Fixed an issue that prevented guide and template pages from opening
• Restored these pages so they load correctly again

Headless and automated OpenHTF runs can now answer operator prompts ahead of time, so a prompt no longer stalls an unattended run.

• Fixed operator prompts ignoring pre-baked input values during automated runs, which caused them to wait and eventually time out.
• Added automatic prompt resolution when every required input is supplied up front, matching the behavior of native procedures.

Deployments now build on the Python version your procedure declares, instead of always on 3.12. A procedure pinning requires-python = ">=3.13" previously failed to build with "No interpreter found for Python 3.13".

• Added support for building procedures on Python 3.10 through 3.14, selected from your pyproject.toml requires-python.
• Improved error messages when a version can't be satisfied, pointing you to a supported range instead of failing cryptically.
• Kept the default at 3.12 when requires-python is omitted, so existing procedures build unchanged.

Test stations that need root access to their hardware can now start automatically at boot. Previously enabling launch on boot as root failed because the station installed a user-level service.

• Added automatic system-service install when the station runs as root, so launch on boot works without a login session.
• Hid the on-screen kiosk option for root stations, which have no display, and made clear that these stations are controlled from the dashboard.
• Showed a clear, actionable message instead of a raw systemd error when launch on boot cannot be enabled.

The CLI kiosk and the dashboard operator UI now support attachment images. Attach a board photo, probe shot, or failure close-up during a run and it shows inline next to the phase instead of as a bare filename, so the operator can compare it against the unit while the run is live.

• Added inline image rendering for run attachments in the CLI kiosk (served locally) and the dashboard operator UI (served after upload)
• Fixed station runs so attachment images reach the dashboard, matching OpenHTF and Robot runs
• Improved deployment history to show who ran a CLI deploy instead of "unknown"