25 lines
1.3 KiB
Markdown
25 lines
1.3 KiB
Markdown
# 0009: The primary work region uses responsive vertical lanes
|
||
|
||
Status: accepted for the native vertical slice.
|
||
|
||
The middle 60% work region shows one vertical lane in compact windows, three at
|
||
normal desktop widths, and five when at least 2800 px remains after the sidebar.
|
||
A 3440 px ultrawide therefore presents five lanes. A sliding window over the six
|
||
comparison panes always keeps the selected pane visible.
|
||
|
||
This is not a return to the original 2×3 dashboard. Every lane receives the full
|
||
work-region height, the surrounding context and decision bands remain stable,
|
||
and only the selected lane owns keyboard input. Clicking a lane selects it. Pane
|
||
processes and output continue independently of selection.
|
||
|
||
Terminal geometry is computed from the actual width of one lane, including gaps
|
||
and insets. The selected real PTY is resized through the runtime actor when the
|
||
responsive lane count or window bounds change. On the 3440×1440 reference
|
||
display the current fixed-cell spike derives approximately 71 columns by 40
|
||
rows per lane.
|
||
|
||
The first actor slice still owns one real PTY and five deterministic comparison
|
||
surfaces. Promoting the runtime boundary from one actor to a pane-indexed session
|
||
registry is required before all five visible terminal lanes can own independent
|
||
real processes.
|