naps62-yoloandClaude Opus 4.7
080f961238
ci / rust (push) Failing after 3m7s
`maestrod` running from a stripped systemd env leaves the spawned shell without `TERM`/`COLORTERM`, and the pane process inherits tmux's `default-terminal` (which defaults to `screen`, 8 colors). Browser attaches via xterm.js render ANSI sequences as plain text. Fix: - `Tmux::new_session` now passes `-e TERM=xterm-256color -e COLORTERM=truecolor` to `tmux new-session`. - New `Tmux::set_option_global` chains `start-server \; set-option -g` so it works before any session exists; the daemon calls it on startup to set `default-terminal=tmux-256color`. Operators wanting 24-bit color should add `set-option -ga terminal-overrides ",xterm-256color:RGB"` to their own tmux config — left out of the daemon since that's operator territory. Tests: - Unit: `new_session_args` returns the expected argv including the `-e TERM=…` / `COLORTERM=…` pair. - Integration: spawn a session under an isolated tmux server, set `default-terminal`, run `printenv` + `tput colors`, assert the pane sees `TERM=tmux-256color`, `COLORTERM=truecolor`, and 256 colors. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>