hermes - 💡(How to fix) Fix Kanban dashboard Default board can render current non-default board cards [2 pull requests]

Summary

The Kanban dashboard board selector can say Default while the card grid is actually loaded from another current board (reproduced with a newly-created trading board). The header/count and rendered columns become inconsistent, so users cannot reliably switch back to the default board from the UI.

Repro

1. Open dashboard at /kanban.
2. Create a second board, e.g. trading, with at least one card.
3. Make trading the backend current board (board creation with switch enabled does this).
4. In the dashboard selector choose Default.

Expected

Selecting Default pins API/WebSocket traffic to the default board, and the grid shows default-board cards.

Actual

The selector/header can show Default, but the dashboard fetches /api/plugins/kanban/board without board=default. The backend falls through to the CLI/gateway current-board pointer, so it returns the non-default board (e.g. trading) and live events from that board can also bleed in.

Root cause

plugins/kanban/dashboard/dist/index.js omits the board query param when the selected board is default in both REST requests and the WebSocket subscription. That is only safe if the backend current-board pointer is also default.

Fix direction

Always include board=<selectedSlug> for dashboard requests, including board=default, and include it in the WebSocket query too. The backend already accepts board=default and correctly resolves the default DB.