Defend the number the README publishes, and stop quoting the best of three

[tonytonycoder11]

Found while checking whether the repository's About description was still true. Two of its numbers were
not, and one of them was a claim nothing was defending.

A measurement with no assertion under it

The native-image job measures the time from process start to first search, prints it, and passes
whatever it says. The only failure path is a missing value. So a dependency that began doing real work at
startup could have taken it to 300 ms and no build would have gone red, while the README's comparison
table kept saying 37 ms.

The paragraph under that table claims the job stops the sentence quietly becoming false. That was true of
the reflection claim, because --no-fallback fails the build, and it was not true of the time.

It now fails over a 75 ms ceiling. Loose deliberately: across recent runs on main the measurement lands
between 29 and 42 ms on a shared runner, so the ceiling leaves room for a noisy neighbour and still
catches the thing worth catching, which is a regression that doubles it.

37 ms was not the number any more

The last four runs on main measured 31, 29, 42 and 34. A single frozen figure for a measurement that
moves was going stale by design, and it had. The table now states the bound the build defends and says
where the measurement usually lands, which is a claim that stays true without anyone editing it.

The CLI is not 5.7 MB

That is the macOS arm64 binary. Windows is 6.8 MB and Linux x64 is 14.1 MB.

Quoting the smallest of three without saying so is bad anywhere, and the paragraph it sits in is the one
added in 2.3.0 to stop a reader concluding from an ARM target, a fast cold start and a small binary that
Kdrant runs as the vector database. Picking a winner inside that argument undercuts it.

Also updated, outside this PR

The repository About description carried both numbers and did not mention the MCP server, while the repo
topics already carry mcp and model-context-protocol. It now reads:

Coroutine-first Kotlin client for Qdrant, plus an MCP server for it that is a static binary instead of a
Python runtime. Suspend APIs, a typed filter DSL, REST or opt-in gRPC behind one seam, nine platforms
including iOS and Windows, and a GraalVM native image with no reflection config to write.

The two fragile numbers are gone from it. They live in the README, next to the job that produces them and
now defends them, which is where a number that changes on every push belongs.

[trueup-by-nacode-studios]

This pull request adds no capability the code did not already have.

_{2 files read · 1051 ms · against 431702e · engine 1.4.1}