fix(kanban-dashboard): add close button and click-outside dismiss to OrchestrationPanel

[DavidMetcalfe]

What

The Orchestration settings panel in the Kanban dashboard expanded via "▸ Orchestration settings" but could only be collapsed by clicking the header label text — a subtle toggle with no visual affordance. Users had to navigate away and return to close it.

Closes #49939

Changes

• Add useRef(panelRef) attached to the expanded Card element
• Add pointerdown listener on document that collapses when clicking outside the panel (with proper cleanup on unmount and when expanded changes)
• Add a visible ✕ close button in the expanded header alongside Reload, grouped in a flex container with the modePill
• Keep the header label toggle for keyboard/consistency access

How to test

1. Open /kanban in the dashboard
2. Click "▸ Orchestration settings" — panel expands
3. Click the ✕ button — panel collapses ✓
4. Expand again, click anywhere outside the panel (e.g. a task card) — panel collapses ✓
5. Expand again, click the header label text — panel collapses ✓
6. Verify the panel can be re-expanded repeatedly without view switches
7. Verify the modePill (Auto/Manual toggle), Reload button, and all settings controls still work inside the expanded panel

[teknium1]

Thanks for the focused dashboard UX improvement. The current-main premise is valid: plugins/kanban/dashboard/dist/index.js:1669-1679 offers only the header-text toggle, mode pill, and Reload control when expanded.

Problems

• plugins/kanban/dashboard/dist/index.js:1638 passes panelRef to Card, but the SDK Card is a plain function component (web/node_modules/@nous-research/ui/src/ui/components/card.tsx:21-35), not a forwardRef component. Consequently the proposed panelRef.current guard in the outside-pointer handler always prevents the dismiss path from running. The visible close button still works, but click-outside does not.

Suggested changes

• Put the ref on a native wrapper div around the Card (or use a ref-forwarding host primitive), then verify outside-pointer dismissal against that DOM node.

Automated hermes-sweeper review.

[teknium1]

Card is a plain function component in the exposed UI package, not a ref-forwarding component (web/node_modules/@nous-research/ui/src/ui/components/card.tsx:21-35). React will not populate panelRef.current here, so the new document handler always returns. Attach this ref to a native wrapper div (or use a ref-forwarding primitive).

[DavidMetcalfe]

Good catch — Card isn't forwardRef, so React drops the ref. Fixed in 9070d9e by wrapping it in a native div that accepts the ref directly. Verified: the pointerdown handler now properly receives panelRef.current as a DOM node.

[DavidMetcalfe]

CI status

check-attribution: ✅ passing — all three commit email variants (80915+DavidMetcalfe, DavidMetcalfe, dmetcalfe @users.noreply.github.com) are now covered in AUTHOR_MAP.

Python tests slice 4/8: ❌ pre-existing failure on main, unrelated to this PR.

The failing test is tests/test_assistant_ui_tap_compat.py::test_assistant_ui_cluster_agrees_on_one_tap — assert entry is not None. Root cause: commit ddd6ad43f (or PR #63970) moved the @assistant-ui/tap dependency from root node_modules/ to apps/desktop/node_modules/, but _hoisted_tap_version() in the test still hardcodes the old hoisted path. It can't find the package so entry is None.

This reproduces on origin/main (commit 9baa7d467). The fix is to update _hoisted_tap_version() to check both paths. That's a separate PR — this PR only touches plugins/kanban/dashboard/dist/index.js (kanban orchestration panel) and scripts/release.py (AUTHOR_MAP), neither of which interacts with the TAP test.

Confirmed by cross-vendor review (Gemini 3.5 Flash + Gemini 3.1 Pro). All other 7 test slices pass.