fix(app,web): put the caret in the target picker's search when it opens

[khagele]

Closes #714

What

Reaching a node by name took three actions: open the picker, press its search field, type. Opening now puts the caret in the search in the same tap, so a phone raises its keyboard and the next keystroke searches.

app. createTargetList gets open(), which the target chip calls where it called reset():

• the query is cleared, so every open starts from the full list; a query left from the last open used to come back with a list narrowed by it and nothing saying why;
• the list repaints at once when there was a query, so the narrowed list never shows for the second until the next tick;
• #ts-search takes the focus (preventScroll).

A sheet that closes with the focus inside lets go of it (releaseFocus), so the caret and the keyboard do not stay on a hidden field.

web. wirePopover takes a focusEl. The sender picker passes #f-sender, which keeps its value: on web it is the sender filter itself, bound to ?sender=. Closing with the focus inside hands it back to the toggle; that holds for the hunter and ignore pickers too, which pass no focusEl.

Verification

• targetlist.test.js (new): open() focuses the field, clears the query and repaints. Each line of open() red when removed.
• multiselect.test.js: focus on open with preventScroll and the value kept; focus back to the toggle on Escape, and left alone when it was elsewhere. Red under mutation.
• e2e/targetpicker.spec.js: in Chromium the caret is in #f-sender after the toggle, typing lands there, Escape hands focus back. Red without the focusEl.
• App at 390x844 with eight senders: focus on #ts-search, dik narrows to one row, the field and the matches stay above a 300 px keyboard; reopening shows an empty field and the full list.
• app: 1625 tests green, eslint clean
• web: 765 tests green, full e2e 298 passed

🤖 Generated with Claude Code

[khagele]

Amended (cb3f212): in the app, a sheet that closes with the focus inside now hands it back to its toggle (releaseFocus(sheet, toggle) in app.js), as wirePopover does on web. Before, it blurred to the body, so a keyboard user on desktop lost their place. App: 1625 tests, eslint, build.

[efiten]

Review before merge: two points to change, two suggestions. Found by reading the code at cb3f212, not run in a browser.

1. Escape in the web sender picker can clear the sender filter (change requested)
web/multiselect.js:264 closes the panel on Escape without preventDefault(), and #f-sender is type="search" (web/index.html:144). In Chromium and WebKit, Escape in a non-empty search field clears it and fires input, which map.js binds to ?sender=. Before this PR the focus stayed on the toggle, so Escape only closed the panel. Now the caret is in the field, so open, glance, Escape can wipe an active sender filter.
Proposed: e.preventDefault() before close(), and in e2e/targetpicker.spec.js assert that #f-sender still holds cc after the Escape.

2. The app sheet's own close button bypasses releaseFocus (change requested)
buildTargetSheet in app/src/app.js still wires ts-close as sheet.hidden = true. On desktop Chrome the click focuses #ts-close, and hiding the sheet then drops focus to the body: the case the amend describes fixing. The same path exists where filter-pill and settings-btn hide the target sheet directly (app.js:3932, 3942).

3. Suggestion: a test for releaseFocus
The helper and its two call sites have no test (AGENTS.md §5.1). A fake-DOM test like the web one would pin it.

4. Suggestion: the repaint test
targetlist.test.js checks that the list goes from 1 child to 0, not that browseEl becomes visible again, which is the part a user sees.

[khagele]

Pushed 5d6d451 for the review, rebased on master. Per point:

1. Escape clears the sender filter. wirePopover calls preventDefault() before close(). e2e/targetpicker.spec.js now asserts that #f-sender still holds cc after the Escape (it read "" before the fix), and the unit test checks defaultPrevented.
2. Close paths that bypassed it. closeSheet(sheet, toggle) in app/src/sheetfocus.js hides a sheet and hands the focus back to its toggle when it was inside. Every path that hides one of the three sheets goes through it: the close buttons (fs-close, ts-close, ss-close), a toggle closing its own sheet, a sheet closing the other two when it opens, a tap outside, and the Disconnect and "How to use" buttons in Settings. No sheet.hidden = true is left in app.js.
3. A test for it. sheetfocus.test.js with a fake sheet and toggle: focus inside goes to the toggle, focus elsewhere stays. Red with the focus line removed.
4. The repaint test. It now passes a browseEl and checks that it is hidden under the query and visible again after open(). Red without the repaint.

App: 1632 tests, eslint, build. Web: 765 tests, eslint, Playwright 298 passed. The app's sheets were not clicked through in a browser.