docs: polish README and trim migration commentary

Author: teovl

README.md

@@ -1,23 +1,14 @@
 # libpilot
 
-Pilot Protocol C ABI. Builds a shared library
-(`libpilot.dylib` / `libpilot.so` / `libpilot.dll`) that other
-language SDKs link against via FFI:
+Pilot Protocol C ABI. Builds a shared library (`libpilot.dylib` / `libpilot.so` / `libpilot.dll`) plus a C header (`libpilot.h`) that other language SDKs link against via FFI.
 
-- **pilot-protocol/sdk-node** — Node.js via `koffi`
-- **pilot-protocol/sdk-python** — Python via `ctypes`
-- (future) Swift, Rust, etc.
+The library embeds a full pilot daemon plus all the standard plugins (handshake, policy, runtime, skillinject, trustedagents, dataexchange, eventstream, webhook). FFI clients get a single in-process pilot node.
 
-The library embeds a full pilot daemon plus all the standard plugins
-(handshake, policy, runtime, skillinject, trustedagents, dataexchange,
-eventstream, webhook). FFI clients get a single in-process pilot node.
+## Consumers
 
-## Layout
-
-| File | What it does |
-|---|---|
-| `bindings.go` | The exported `//export` C functions: `pilot_init`, `pilot_send`, `pilot_recv`, `pilot_close`, etc. |
-| `embedded.go` | In-process daemon construction (runtime + plugins). |
+- [sdk-node](https://github.com/pilot-protocol/sdk-node) — Node.js via `koffi`
+- [sdk-python](https://github.com/pilot-protocol/sdk-python) — Python via `ctypes`
+- [sdk-swift](https://github.com/pilot-protocol/sdk-swift) — Swift via C interop
 
 ## Build
 
@@ -26,19 +17,15 @@ make build           # produces libpilot.<ext> + libpilot.h
 make clean
 ```
 
-The output `libpilot.h` is the C header consumers include or generate
-bindings against. The `.dylib`/`.so`/`.dll` is the runtime library.
+The output `libpilot.h` is the C header consumers include or generate bindings against. The `.dylib` / `.so` / `.dll` is the runtime library.
 
-## Releasing
+## Layout
 
-Release workflow builds binaries for `linux/{amd64,arm64}`,
-`darwin/{amd64,arm64}`, `windows/amd64` and attaches them to the
-GitHub release. SDK repos pull the matching artifacts in their own
-release pipelines.
+| File | What it does |
+|---|---|
+| `bindings.go` | Exported `//export` C functions: `pilot_init`, `pilot_send`, `pilot_recv`, `pilot_close`, etc. |
+| `embedded.go` | In-process daemon construction (runtime + plugins). |
 
-## Why a separate repo
+## Releases
 
-CGo binaries don't compose well with pure-Go modules — putting the
-`cgo` blob in the protocol repo's main module would force every
-consumer onto a CGo-capable toolchain. Splitting it out keeps the
-protocol modules pure-Go.
+The release workflow builds binaries for `linux/{amd64,arm64}`, `darwin/{amd64,arm64}`, and `windows/amd64` and attaches them to the GitHub release. SDK repos pull the matching artifacts in their own release pipelines.