docs: document Server.connect() method

- Add Server.connect() feature to CHANGES file
- Add comprehensive example to quickstart.md showing connect() as cleaner
  alternative to has_session/new_session pattern
- Add control-mode compatibility example in topics/control_mode.md
- All doctests pass (29 tests in quickstart and control_mode docs)

Author: tony

CHANGES

@@ -40,6 +40,10 @@ _Future release notes will be placed here_
   notification parsing (layout changes, unlinked windows, client detach/session change,
   session rename, paste-buffer events), and stats while keeping existing
   `Server/Session/Window/Pane.cmd` return type (`tmux_cmd`) stable. (#605)
+- `Server.connect()`: New convenience method for session management. Returns an
+  existing session if found, otherwise creates a new detached session. Simplifies
+  common session reuse patterns and works transparently with both subprocess and
+  control-mode engines.
 
 ### Compatibility
 

docs/quickstart.md

@@ -280,6 +280,41 @@ Session($1 foo)
 
 to give us a `session` object to play with.
 
+## Connect to or create a session
+
+A simpler approach is to use {meth}`Server.connect()`, which returns an existing
+session or creates it if it doesn't exist:
+
+```python
+>>> session = server.connect('my_project')
+>>> session.name
+'my_project'
+
+>>> # Calling again returns the same session
+>>> session2 = server.connect('my_project')
+>>> session2.session_id == session.session_id
+True
+```
+
+This is particularly useful for:
+
+- Development workflows where you want to reuse existing sessions
+- Scripts that should create a session on first run, then reattach
+- Working with both subprocess and control-mode engines transparently
+
+Compare with the traditional approach:
+
+```python
+>>> # Traditional: check then create
+>>> if server.has_session('my_project'):
+...     session = server.sessions.get(session_name='my_project')
+... else:
+...     session = server.new_session('my_project')
+
+>>> # Simpler with connect()
+>>> session = server.connect('my_project')
+```
+
 ## Playing with our tmux session
 
 We now have access to `session` from above with all of the methods

docs/topics/control_mode.md

@@ -46,6 +46,29 @@ Control mode creates a bootstrap tmux session named ``libtmux_control_mode``.
 If your code enumerates sessions, filter it out.
 :::
 
+## Session management with Control Mode
+
+The {meth}`Server.connect()` method works seamlessly with control mode:
+
+```python
+from libtmux._internal.engines.control_mode import ControlModeEngine
+from libtmux.server import Server
+
+engine = ControlModeEngine()
+server = Server(engine=engine)
+
+# Reuses session if it exists, creates if it doesn't
+session = server.connect("dev-session")
+print(session.name)
+
+# Calling again returns the same session
+session2 = server.connect("dev-session")
+assert session2.session_id == session.session_id
+```
+
+This works transparently with both control mode and subprocess engines, making it
+easy to switch between them without changing your code.
+
 ## Parsing notifications directly
 
 The protocol parser can be used without tmux to understand the wire format.