Polish live workbench shell layout
This commit is contained in:
@@ -2207,3 +2207,31 @@ Limitations:
|
||||
|
||||
Next recommended pass:
|
||||
- Add export history filtering or retention controls if artifact history continues to grow during demo runs.
|
||||
|
||||
## Sprint 55 live visual shell polish (2026-06-17)
|
||||
|
||||
Changed:
|
||||
- Performed a Browser-based visual audit of the live Tower workbench at `http://192.168.10.150:1202`.
|
||||
- Confirmed the main visual defect was the cramped three-column desktop shell: left navigation, central workspace and inspector competed for width at 1280px.
|
||||
- Compacted the sticky top context bar and left navigation.
|
||||
- Changed the standard desktop breakpoint so the inspector moves below the workspace up to 1360px, while remaining a side panel on wider displays.
|
||||
- Made the Map toolbar wrap responsively instead of forcing four controls into a narrow row.
|
||||
- Added a workspace-change scroll reset so switching pages starts at the workspace heading instead of inheriting stale scroll position.
|
||||
- Added regression coverage for the standard desktop shell width and scroll-reset behavior.
|
||||
|
||||
Tested:
|
||||
- Local Browser visual audit against `http://127.0.0.1:5177` using the live Tower API proxy.
|
||||
- Verified Overview, Data, Map and Exports workspaces visually after the shell changes.
|
||||
- Browser console error/warning check returned no entries.
|
||||
- `cd frontend && npm run typecheck`
|
||||
- `cd backend && python -m pytest tests/test_sprint53_selection_ergonomics.py tests/test_sprint50_workspace_usability_polish.py -q`
|
||||
- `cd frontend && npm run build`
|
||||
|
||||
Open:
|
||||
- Run full readiness, deploy Tower and verify the live visual shell on `http://192.168.10.150:1202`.
|
||||
|
||||
Limitations:
|
||||
- This pass remains UI shell polish only. It does not add features, change API contracts, alter migrations, fetch live providers or enable new AI models.
|
||||
|
||||
Next recommended pass:
|
||||
- Continue with export history filtering or retention controls if repeated demo runs keep growing artifact history.
|
||||
|
||||
Reference in New Issue
Block a user