v0.6.1

Browser fixes: dialogs, SPA readiness, child tabs, Tab key, Chrome reconnect

Most of this came from issues and pull requests by @ElliotDrel. Thank you.

• Snapshots scope to the open dialog (#18, #21). browser_snapshot no longer spends its 250-element budget on controls hidden behind a modal. It scopes to the topmost visible dialog and skips hidden, aria-hidden and inert subtrees. A select's options rendered in a portal outside the dialog stay in scope. Results report total, truncated and nextOffset; pass offset/limit to page through.
• Wait for the UI you expect (#19, #21). browser_click, browser_type, browser_press_key and browser_navigate (with return_state: true) and browser_snapshot accept wait_for_selector and wait_timeout_ms. Readiness is reported separately from the action's own result (met, timeout, error, not_requested), so a slow dialog no longer looks like a click that did nothing. Selectors that test the value attribute are refused: they could reveal a password one guessed character at a time.
• Tabs the agent's clicks open are the agent's (#14). A target=_blank link or popup opened by an agent click or key press joins that task's tabs and group, and its cleanup closes it. Tabs you open yourself stay yours.
• Tab moves focus in background tabs (#20). Chrome skips focus traversal in an unfocused tab, so the keystroke used to do nothing while the tool reported success. The extension now moves focus to the next field and says which element has it, or fails if focus can't move.
• Chrome reconnects after the server restarts (#16, #17). On Windows and Linux the native-messaging relay now exits when the server goes away, so the extension reconnects instead of keeping a dead connection.
• null for an optional argument means the same as leaving it out. If the extension is older than the server, results say so.

32 tools. Update the Chrome extension: the new options and fixes need it, so reload it after updating.