tmux log-file silent failure when deployment script lacks write permission

Goal

Capture the complete output of a deployment script running inside a tmux pane so that a later post‑mortem can correlate the exact error messages and exit status.

Constraints and uncertainty

The log-file option (global or per‑window) appends raw pane output—including ANSI escape sequences—without timestamps or rotation. Logging begins only for panes created after the option is set; existing panes are unaffected. If the target log file cannot be written due to permission problems, tmux fails silently and no output is recorded, leaving no indication that logging stopped.

Questions

1. What is the most reliable way to verify that logging is active for a specific pane before starting a long‑running deployment?
2. How can ANSI escape sequences be stripped or rendered after the fact so that error messages remain readable in the log file?
3. Is there a built‑in mechanism or common pattern to rotate or size‑limit the log file without external tooling?