FUTURE: add TUI as first UI milestone

FUTURE.md

@@ -23,6 +23,16 @@ Talks to the daemon over the IPC port. The separation means the UI is replaceabl
 
 Target: a web frontend (React or similar) wrapped in a native binary using a Tauri-style approach — native packaging, OS webview, no Electron weight. Avoids the wxWidgets ugliness of the old wxWASTE fork and the Qt licensing headaches of the VIA fork.
 
+#### TUI (near-term)
+A terminal UI is worth building first, as a `cmd/tui` using [Bubble Tea](https://github.com/charmbracelet/bubbletea). Since the IPC contract is already the full boundary, a TUI is just another client — connect to `127.0.0.1:17337`, receive the `state_snapshot`, then funnel incoming events into Bubble Tea's update loop. Incoming mesh events map naturally onto its Elm-style message model.
+
+Benefits over jumping straight to a native GUI:
+- Works over SSH; zero packaging complexity
+- Validates the full IPC protocol and message flow end-to-end
+- Useful day-to-day while the native UI is still future work
+
+The TUI doesn't replace the long-term GUI — it won't serve non-technical friends — but it's the right first UI milestone.
+
 ---
 
 ## Protocol Modernization