hermes - 💡(How to fix) Fix [Bug] Kanban dashboard DELETE /tasks/:id ignores board parameter — 404 on non-default boards

Bug Description

When switching to a non-default Kanban board in the dashboard and clicking the delete (trash) button on a task, the API returns 404: {"detail":"task <id> not found"}. The task exists on the current board but the DELETE request does not include the board query parameter, so the backend looks up the task on the default board.

The same bug affects the "Delete selected" (multi-select) function.

Steps to Reproduce

1. Create a second board: hermes kanban boards create my-board
2. Switch to the new board: hermes kanban boards switch my-board
3. Create a task on it: hermes kanban create "test task"
4. Open the dashboard and switch to my-board (board switcher in the top-right)
5. Click the delete (trash) icon on the task
6. Expected: Task is deleted
7. Actual: Toast/error shows 404: task t_xxx not found

Root Cause

The frontend's deleteTask() callback at plugins/kanban/dashboard/dist/index.js line 915 sends a DELETE request without the board query parameter:

// ❌ Missing board parameter
SDK.fetchJSON(`${API}/tasks/${encodeURIComponent(taskId)}`, {
  method: "DELETE",
})

The backend at plugins/kanban/dashboard/plugin_api.py line 754 accepts an optional board query parameter and falls back to the default board when absent:

@router.delete("/tasks/{task_id}")
def delete_task(task_id: str, board: Optional[str] = Query(None)):
    board = _resolve_board(board)     # → None → default board
    conn = _conn(board=board)          # → searches default board DB
    ok = kanban_db.delete_task(conn, task_id)  # → 404

Other endpoints (GET /board, PATCH /tasks/:id) already send the board parameter correctly — only DELETE is missing it.

Fix (local patch)

Both deleteTask (single) and deleteSelected (multi-select) need to append ?board=<current_board>:

const url = board
  ? `${API}/tasks/${encodeURIComponent(taskId)}?board=${encodeURIComponent(board)}`
  : `${API}/tasks/${encodeURIComponent(taskId)}`;

The board dependency is already in the useCallback's dependency array ([board, loadBoard, t]) — it just wasn't used in the request URL.

Environment

• Hermes Agent version: v0.13 (multi-board feature)
• Browser: any (tested on Chromium/Firefox)
• The bug only manifests with non-default boards — users on the default board never hit it