fix(canvas): keep a hovered terminal's keyboard after the pointer leaves (sloppy focus)

[eneskirca]

Problem

With the default Terminal focus follows pointer (ON), hovering a terminal for the pan-hover delay gave it the keyboard — and moving the pointer off it took the keyboard straight back (onBodyLeave blurred the xterm and dropped the node's active flag + presence focus). Typing into a terminal while the mouse rested on the canvas, the sidebar, or on its way to another card silently went nowhere.

Change — sloppy focus

The hover dwell now only takes the keyboard. The terminal keeps it until:

• another terminal takes it (its own dwell, or a click), or
• the user clicks another node, the empty canvas, or a field.

How:

• onBodyLeave no longer blurs/releases in either mode; in focus-follows-pointer mode it only re-arms the hover guard (pointerLeaveRearmsGuard), so a pass-over scroll still pans the canvas until the next dwell.
• Release follows DOM focus via the existing useClickToFocus hook (feature request: option to disable X Window focus-follows-pointer (Mac-style click to select what UI element has the input focus) #757), which now runs in both modes (the enabled param is gone). Its setArmed is a no-op in focus-follows-pointer mode (focusDrivesGuard) — the guard stays a pointer contract there, so a ⌘K / sidebar release can't strand an armed guard under a resting pointer, and a header-drag reclaim can't drop it while the pointer is elsewhere.
• A dwell onto a node whose ⌘M view covers its xterm can't take the keyboard itself, so it blurs the previous terminal's xterm (dwellBlursForeignTerminal) instead of leaving that pane receiving keystrokes while another node reads as active. Stickies/editors/fields keep their caret, as before.
• Settings → Behavior copy, CLAUDE.md and the module docs updated.

Click to focus (setting OFF) is unchanged.

Surfaces

• Desktop + Server Edition: same renderer code — both get it.
• Kanban card modal: N/A (ModalTerminal has no hover guard).
• Mobile: N/A (no hover).

Tests

• Pure decisions (terminalFocusMode.test.ts): pointerLeaveRearmsGuard, focusDrivesGuard, dwellBlursForeignTerminal, plus wiring checks that onBodyLeave contains no blur / setActive(id, false) / releaseFocus.
• Hook (useClickToFocus.test.tsx): a terminal the pointer has left keeps the keyboard and stays active; another terminal's xterm taking focus releases it.
• Mutation-checked: re-adding the blur in onBodyLeave, or ungating setArmed, turns the suite red.
• npm run typecheck / full renderer suites on this box: only pre-existing env failures from a stale shared node_modules (ssh2 missing, monaco 0.52 vs ^0.57) — identical on clean main.

Mac verification owed

1. Hover terminal A until it focuses, move the mouse to the empty canvas, type → text lands in A; A stays active.
2. With the mouse resting on A's header / the sidebar, type → still A.
3. Hover terminal B until it focuses → keyboard moves to B; A's active state clears.
4. Click the empty canvas → keyboard leaves A (Backspace no longer types into it).
5. Mouse back over A and scroll immediately → canvas pans until the dwell elapses (guard re-armed).
6. Open ⌘M on B, then hover B from A → typing no longer goes into A.
7. Drag A by its header after typing in it → Backspace still goes to A, not "delete node".

🤖 Generated with Claude Code