bug: headed silently ignored on existing session

[louisdegeestldg]

When a session already has a headless daemon running, passing --headed on the next command does nothin: no window appears, no error, no warning.

Reproduction:

agent-browser open https://example.com --session test
# later...
agent-browser open https://other.com --headed --session test
# no window. still headless.

Closing the session first works around it:

agent-browser close --session test
agent-browser open https://example.com --headed --session test
# window appears

Looks like ensure_daemon() returns early when the socket is already responsive and never passes the headed preference to the running daemon. The env var (AGENT_BROWSER_HEADED) gets frozen at daemon spawn time.

Would be great if passing --headed to an existing headless session either relaunched the browser or at least printed a warning.

v0.16.3, macOS arm64