lumbridge-public/lumbridge-code
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: add responsive ultrawide work lanes
CI / rust (push) Successful in 2m3s
Details

Browse Source
This commit is contained in:
karti
2026-08-31 17:46:18 -07:00
parent e7ca1d0a73
commit 3f15b13312
11 changed files with 304 additions and 74 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/decisions/0008-primary-terminal-3x1-workspace.md
+8 -9
View File
@@ -2,22 +2,21 @@
Status: accepted for the native vertical slice.
Lumbridge defaults to three vertical bands in one column. The top 20% exposes
Lumbridge defaults to three horizontal bands in one column. The top 20% exposes
pane, agent, tools, context, goal, target, and attention state. The middle 60%
belongs to the active terminal or work surface. The bottom 20% holds answers,
choices, chat, approvals, and the local-analyst boundary.
is the terminal-first work region. The bottom 20% holds answers, choices, chat,
approvals, and the local-analyst boundary.
This composition favors the surface where engineers type and read for most of
the day. It keeps context and decisions visible without making six equally sized
cards compete for attention. Pane selectors and keyboard shortcuts switch the
large work surface. Users may later create deliberate splits or dashboard grids,
but those are workspace choices rather than the default visual hierarchy.
This composition favors the region where engineers type and read for most of the
day. It keeps context and decisions visible without making every surface a small
dashboard card. The middle region may contain a responsive number of vertical
work lanes under decision 0009; the selected lane alone owns keyboard input.
The framework spike retains six updating surfaces even when five are offscreen.
That preserves the earlier streaming and reducer workload for performance
comparison. Hidden surfaces do not receive keyboard input merely because they
continue to update.
Window geometry determines the middle band's terminal rows and columns. The UI
Window and lane geometry determine each terminal's rows and columns. The UI
resizes the terminal engine and PTY through the bounded runtime actor; it does
not resize only the text view or infer terminal wrapping after the fact.
docs/decisions/0009-responsive-ultrawide-work-lanes.md
+24
View File
@@ -0,0 +1,24 @@
# 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.