Merge lane UX: run console 404s

Found while testing the merge lane on main (Task 5573). 1. The web console of a running merge-lane run (Merge lane tab › Runs › ● button, and the task's 🪟 button) shows "Connection: slot not found": `GET /api/console/jaah/1/open?kind=clauded&node=h2` answers 404 for run 5836, which was running on h2. Opening a running lane run's console must attach to its pane. 2. A lane run's task Details names no node or slot, so an operator cannot tell where it ran. Show the node, and the slot, on the run row and on the task. 3. The Runs list shows only a duration and ✓/✕. Show the failure reason (e.g. "gate sandbox would not start on gmind-shared-1") and the moved-off node, inline on the row. 4. A run whose node was excluded after a `node_fault` gives no sign of it in the Merge lane tab. Show "node X skipped for lane runs until HH:MM". 5. A lane task opened in the Gmind org view answers "Task not found", because lane tasks are hidden. A link from the Merge lane tab must open the task in any org view that can see the tab.

Merge lane UX: run console works across orgs (operator attaches), runs show node/slot, failure, moved-off node and skipped nodes; lane tasks open from the tab. PR #5087 merged, Jaah Deploy green. 7 UI follow-ups in report.