v3.0.802026-05-29
Terminal paint rollback
Turns the new global terminal render scheduler back into an opt-in path after 3.0.79 still allowed active Claude and Codex panes to sit blank or partially painted.
- Agent panes return to the stable renderer path. BridgeSpace now defaults back to the per-terminal render loop used before 3.0.74, restoring the known-good terminal paint behavior from 3.0.72 while the scheduler is reworked behind an opt-in flag.
Changed
- The global terminal render scheduler is now opt-in via `localStorage['bridgespace.terminalRenderScheduler.v1'] = 'on'`; default builds use the older per-terminal render loop until the scheduler has a dedicated xterm DOM regression harness.
Fixed
- Fixed the remaining terminal paint regression where Claude, Codex, and other full-screen agent panes could keep running while the visible terminal stayed blank or only partially painted.