Runner v0.4.7

Runner 0.4.7 stops backend-started missions from destroying their own scrollback, and gives the packaged app the diagnostics to finally pin the launch-resume width bug.

Bug Fixes

• Missions started from MCP keep their scrollback. A mission started by an agent through the MCP mission_start tool forked every slot terminal at 80×24 — the first time you opened a slot tab, the real-width resize purged the session's entire output ring, and minutes of the agent's transcript vanished. The app now records the mission pane's real grid whenever the frontend measures it and uses that as the fork size for backend-started missions, so the first tab visit is a no-op resize and the history stays. Missions started from the UI were never affected.
• The launch width estimate can no longer lie. When the shell's content area couldn't be measured, the estimator fell back to the full window width — sidebar included — and could also read the wrong element entirely while Settings was open. A failed measurement now abstains, letting the persisted per-session geometry take over instead of a confidently wrong guess.

Improvements

• Launch-resume is now observable in packaged builds. Every session fork logs its width and where that width came from (caller, persisted geometry, mission hint, or default), every width-change ring purge logs old→new columns, and the launch dims pipeline — settle outcome, chosen source, measurement inputs, estimate, and the pane's first real fit — writes a [launch-dims] trace into the rotating log file under ~/Library/Logs. If a restored terminal ever comes back wrong again, the log now says why.

Download

• Apple Silicon: Runner_0.4.7_aarch64.dmg
• Intel: Runner_0.4.7_x64.dmg

Existing installs update in place via the built-in updater.