ab6d6410d5
The cwd was synced only when laneId changed, but a pane can render before GET /api/lanes has answered — split view restores its pane lanes from localStorage, and layout 1 paints before the list loads. With no lane resolved the field fell back to the home suggestion, and since laneId never changed afterwards it stayed there. RunSetup submits that string verbatim to POST /api/lanes/:id/start, so the run was started in the wrong folder. Track the cwd in its own effect keyed on the resolved lane path rather than on laneId, so it re-syncs as soon as the lane is known. The home default now applies only while no lane is selected at all.