Drop TetherKit's TetherClient/SSEClient/Message from the macOS app; drive
tethercore.Engine instead (RoomIdentity still from TetherKit via selective
import). The Mac now gets direct P2P over the RTC data channel for free, and
the native Swift app is no longer a parallel wire-protocol implementation.
Background NSPasteboard polling (auto-send on copy) and write-on-receive are
preserved. Feed UI moves to a FeedItem view-model (RTC messages carry ts=0 →
fall back to local time).
Verified end-to-end against the live server: RECEIVE (bus → Mac pasteboard via
pbpaste) and SEND (pbcopy → bus) both confirmed.
Generalize core/build-ios.sh → build-apple.sh: builds iOS device + sim + macOS
arm64 into one TetherCore.xcframework and vendors it into both apps.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
RoomIdentity.derive() in TetherKit: ubiquityIdentityToken (iCloud account,
portable across devices) → IOKit/identifierForVendor (hardware, device-tied)
→ Keychain UUID (last resort). No user config needed. Both apps auto-connect
on relaunch if server URL was previously saved.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
MenuBarExtra SwiftUI app sharing TetherKit wire layer with iOS.
Auto-sends clipboard changes via NSPasteboard polling (500ms),
auto-writes received messages to NSPasteboard. XcodeGen project.yml.
Both apps build clean; server tested end-to-end with curl.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
