[LaStrada]

The Swift Package Manager manifest is the only integration that works. Everything removed here was either broken or years stale:

• the podspec has been stale at 6.3.2 since 2023, and the Cartfile pinned RxSwift 6.5.0, five minor versions behind the manifest
• no release has ever carried a Carthage archive
• .travis.yml named an Xcode project and scripts that no longer exist, and carried an encrypted secret belonging to the upstream repository
• scripts/all-build.sh and scripts/all-tests.sh drive targets and schemes named RxBluetoothKit iOS, RxBluetoothKit macOS and so on, but this fork names them RxBluetoothKit_Airthings iOS/macOS/tvOS/watchOS — so both fail on their first command. all-tests.sh also pins destinations to iOS 13.6, tvOS 13.4, iPhone 8 and Apple TV 4K.
• .jazzy.yaml named a podspec path that does not exist here, so documentation generation could not have succeeded
• .swift-version, orphaned at 5.0, was only ever read by the CocoaPods and jazzy tooling
• the Pods and Podfile.lock entries in .gitignore have nothing left to ignore

The committed docs/ tree is removed because it was out of date: it was generated for
6.0.0, under the upstream module name, and documented an API five releases old. GitHub
Pages is not enabled on this repository, so it was never served anywhere — and the
Api reference link in the README points at the site upstream still publishes, not at
docs/, so that link is unaffected. The doc comments in Source/ are untouched, and Xcode
surfaces those directly; a generated reference can be reintroduced with DocC if we want one.

Removing the podspec does not retract the pod versions already published — it only means no new
ones. A consumer referencing the podspec by :git/:branch rather than through trunk would lose it.

Two documentation files also stopped matching the manifest, so they are corrected here: the README
listed iOS 9 / tvOS 11 / Xcode 11.4 against a manifest requiring iOS 12 / tvOS 12 / tools 5.9 and now
points at Package.swift instead of restating floors that drift, and HOW_TO_RELEASE.md is rewritten
to describe what actually happens — changelog, merge, tag, release — and to say plainly that raising
the RxSwift range is what decides the version number.

Worth knowing: RxBluetoothKit_Airthings.xcodeproj links RxSwift, Quick, Nimble and RxTest
from $(PROJECT_DIR)/Carthage/Build, so with the Cartfiles gone it can no longer be built at all.
It was already unbuildable from a clean clone without an undocumented carthage bootstrap, and the
README itself said Carthage stopped working around Xcode 12. Deleting those ~31 references without
replacing them would only make the project fail differently, so the choice — migrate it to SPM
dependencies, or drop it along with Tests/ and the two remaining generate-* scripts — is left as
its own change. The Carthage/ ignore lines stay for the same reason: that directory is still named
by the project.

Also out of scope, and worth their own change: scripts/generate-testable.sh emits
@testable import RxBluetoothKit against a module called RxBluetoothKit_Airthings and is still
invoked by three build phases, scripts/generate-mocks.sh defaults to a removed SDK path, and
CHANGELOG.md stops at 6.3.2 while the tags run to 6.3.6.

No source file is touched. swift build passes on both the native and swiftbuild engines.