LAT works: sessions, a browser and a helper The wiki said a LAT session could not be written until somebody had captured one. Two OpenVMS nodes on a wire settled that, and 0.8.9 opens a session on one: SET TERMINAL/INQUIRE identifies veetee as a VT400_Series terminal on an LTA device of its own. Connections gains what a reader needs to use it -- the options, the service browser, and the setcap the helper wants, with what that grant allows spelled out. Architecture gains the helper crate. Roadmap and Releases stop calling LAT the thing standing before 1.0; proving RFC 2217 against real hardware is what is left of M5.
Catch up with RFC 2217, LAT discovery and the recordings Connections said LAT and RFC 2217 were both planned. RFC 2217 shipped in 0.8.7 and LAT discovery works on Linux, so that page now says how to use each, and says plainly that connecting to a LAT service does not work and why: the session has never been captured. Architecture had no vt-lat and a vt-transport that did neither. The roadmap still listed the OpenVMS acceptance recordings as outstanding when there are nine of them replaying in CI, and still capped the signed Windows builds at 0.8.5. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Flatpak, screen readers, faster output, Windows signing
VT500 menu Set-Up, Display Controls and fonts; release 0.7.1
Set-Up, sound, smooth scroll and CRT effects
Update for 0.6.0: Windows, keymap editor, key programming, recordings, fonts
Update for 0.4.0: VT500 models, colour, dual sessions Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016YDmAmHSpzviSn4u4VuqKw
Add veetee documentation Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016YDmAmHSpzviSn4u4VuqKw