docs(docc): remove MainActor references and transport selection details

- Remove @mainactor mentions from SundialKitCombine descriptions
- Remove "all updates happen on main thread" explanations
- Remove automatic transport selection details from connectivity docs
- Preserve actor-based descriptions for SundialKitStream
- Simplify plugin comparison focusing on observation patterns

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

Author: leogdion

Packages/SundialKitCombine/Sources/SundialKitCombine/SundialKitCombine.docc/Documentation.md

@@ -1,14 +1,13 @@
 # ``SundialKitCombine``
 
-Combine-based observation plugin for SundialKit with @MainActor isolation and @Published properties.
+Combine-based observation plugin for SundialKit with @Published properties.
 
 ## Overview
 
-SundialKitCombine provides @MainActor-isolated observers that deliver state updates via @Published properties and Combine publishers. This plugin is designed for SwiftUI projects and apps requiring backward compatibility with iOS 13+.
+SundialKitCombine provides observers that deliver state updates via @Published properties and Combine publishers. This plugin is designed for SwiftUI projects and apps requiring backward compatibility with iOS 13+.
 
 ### Key Features
 
-- **@MainActor Isolation**: All state updates occur on the main thread
 - **@Published Properties**: Direct binding to SwiftUI views
 - **Combine Publishers**: Full reactive programming support
 - **Swift 6.1 Strict Concurrency**: Zero `@unchecked Sendable` conformances

Sources/SundialKit/SundialKit.docc/Documentation.md

@@ -304,9 +304,8 @@ print("Sent via: \(result.context)")
 - Actor-based observers with natural thread safety
 - Ideal for new projects using async/await
 
-**<doc:SundialKitCombine>** (@MainActor + Combine):
+**<doc:SundialKitCombine>** (Combine Publishers):
 - @Published properties and Combine publishers
-- @MainActor isolation for UI safety
 - Compatible with iOS 13+ and SwiftUI projects
 
 Both plugins work with the same core <doc:SundialKitNetwork> and <doc:SundialKitConnectivity> packages - just choose the observation style that fits your project.

Sources/SundialKitConnectivity/SundialKitConnectivity.docc/Documentation.md

@@ -25,7 +25,7 @@ SundialKitConnectivity provides a modern, type-safe wrapper around Apple's [Watc
 
 SundialKitConnectivity provides the foundational WatchConnectivity protocols and messaging types. To use these in your application, you'll need to choose an observation plugin that matches your preferred concurrency model:
 
-- **SundialKitCombine** - For SwiftUI apps using `@MainActor` and Combine publishers
+- **SundialKitCombine** - For SwiftUI apps using Combine publishers
 - **SundialKitStream** - For modern Swift apps using actors and AsyncStreams
 
 Both plugins provide `ConnectivityObserver` classes that handle session management and message routing automatically. The examples below demonstrate how to define and send type-safe messages using each approach.
@@ -130,11 +130,11 @@ With binary serialization, you can transfer complex data structures efficiently.
 
 ### Session Management
 
-Once you've defined your message types, you'll use a `ConnectivityObserver` to manage the WatchConnectivity session and send/receive messages. The observer handles session activation, monitors reachability, and automatically chooses the best transport method based on whether the counterpart device is currently available.
+Once you've defined your message types, you'll use a `ConnectivityObserver` to manage the WatchConnectivity session and send/receive messages. The observer handles session activation and monitors reachability.
 
 #### Using with SundialKitCombine
 
-The Combine-based observer is perfect for SwiftUI applications. It provides `@Published` properties for session state and Combine publishers for incoming messages, making it easy to update your UI reactively. All updates happen on the main thread.
+The Combine-based observer is perfect for SwiftUI applications. It provides `@Published` properties for session state and Combine publishers for incoming messages, making it easy to update your UI reactively.
 
 ```swift
 import SundialKitCombine

Sources/SundialKitNetwork/SundialKitNetwork.docc/Documentation.md

@@ -23,7 +23,7 @@ SundialKitNetwork provides protocol-based abstractions over Apple's [Network fra
 
 SundialKitNetwork provides the foundational network monitoring protocols and types. To use these in your application, you'll need to choose an observation plugin that matches your preferred concurrency model:
 
-- **SundialKitCombine** - For SwiftUI apps using `@MainActor` and Combine publishers
+- **SundialKitCombine** - For SwiftUI apps using Combine publishers
 - **SundialKitStream** - For modern Swift apps using actors and AsyncStreams
 
 Both plugins provide `NetworkObserver` classes that wrap SundialKitNetwork's protocols with reactive APIs. The examples below show how to use each approach.
@@ -32,7 +32,7 @@ Both plugins provide `NetworkObserver` classes that wrap SundialKitNetwork's pro
 
 #### Using with SundialKitCombine
 
-The Combine-based observer is ideal for SwiftUI applications where you want to bind network state directly to your UI. All updates happen on the main thread, making it safe to update views directly from the observers.
+The Combine-based observer is ideal for SwiftUI applications where you want to bind network state directly to your UI.
 
 ```swift
 import SundialKitCombine