Polish live workspace export layout
This commit is contained in:
@@ -2518,3 +2518,28 @@ Limitations:
|
||||
|
||||
Next recommended pass:
|
||||
- Continue with a full-workspace browser smoke and then refine any remaining dense panels found during populated-state review.
|
||||
|
||||
## Sprint 66 Live workspace smoke polish (2026-06-19)
|
||||
|
||||
Changed:
|
||||
- Ran a live browser smoke against `http://192.168.10.150:1202` across Overview, Data, Map, QA/QC, AI Labs, Exports and System.
|
||||
- Captured desktop and mobile screenshots under `artifacts/sprint66-live-workspace-smoke/`.
|
||||
- Confirmed all primary workspaces load with no console warnings/errors and no page-level horizontal overflow.
|
||||
- Tightened Export Center handoff card CSS so action cards and readiness cells wrap by available width instead of forcing cramped three/four-column layouts in the populated Exports workspace.
|
||||
- Added `backend/tests/test_sprint66_live_workspace_smoke_polish.py`.
|
||||
|
||||
Tested:
|
||||
- Red step: `python -m pytest backend/tests/test_sprint66_live_workspace_smoke_polish.py -q` failed on missing width-aware export grid CSS and Sprint 66 log entry.
|
||||
- Live desktop browser smoke: all seven primary workspaces opened, screenshots captured, no console warnings/errors, no horizontal page overflow.
|
||||
- Live mobile browser smoke: all seven primary workspaces opened, screenshots captured, no console warnings/errors, no page-level horizontal overflow. The mobile primary nav intentionally remains a horizontal rail.
|
||||
- Local post-fix browser check against `http://127.0.0.1:5175` with live API proxy: Exports handoff action cards wrap to 2 desktop columns and 1 mobile column, no console warnings/errors and no horizontal page overflow.
|
||||
- `bash scripts/run_readiness_check.sh` (`237 passed`)
|
||||
|
||||
Open:
|
||||
- Deploy Tower and run live browser runtime verification after this CSS polish.
|
||||
|
||||
Limitations:
|
||||
- This is a visual ergonomics hardening pass only. It does not add endpoints, migrations, provider fetching, AI/model behavior or new product capabilities.
|
||||
|
||||
Next recommended pass:
|
||||
- Continue with populated Map/Data interaction polish, especially making it easier to activate the demo vector layer from the map empty state.
|
||||
|
||||
Reference in New Issue
Block a user