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

fix: make workspace panels self contained
CI / rust (push) Successful in 2m54s
Details

Browse Source
This commit is contained in:
karti
2026-08-31 18:02:01 -07:00
parent 3f15b13312
commit 63c9cb6210
10 changed files with 297 additions and 350 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/decisions/0008-primary-terminal-3x1-workspace.md
+15 -14
View File
@@ -1,22 +1,23 @@
# 0008: The default workspace is a primary-terminal 3×1 composition
# 0008: Every workspace panel uses a terminal-first 3×1 composition
Status: accepted for the native vertical slice.
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%
is the terminal-first work region. The bottom 20% holds answers, choices, chat,
approvals, and the local-analyst boundary.
Every Lumbridge workspace panel defaults to three horizontal regions in one
column. The top 20% exposes that pane's agent, tools, context, goal, target, and
attention state. The middle 60% is that pane's terminal-first work surface. The
bottom 20% is that pane's answer, choice, chat, approval, and local-analyst
boundary.
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.
This composition keeps the information needed to understand and steer a process
attached to the same visual object as its terminal. The workspace may contain a
responsive number of these panels under decision 0009; the selected panel 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.
The framework spike retains six updating surfaces even when one is outside the
five-panel ultrawide window. That preserves the earlier streaming and reducer
workload for performance comparison. Hidden panels do not receive keyboard input
merely because they continue to update.
Window and lane geometry determine each terminal's rows and columns. The UI
Window and panel 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.