[tae898]

People mix up the Python embedded bindings (arcadedb, arcadedb-jvm) and the official drivers (arcadedb-driver over HTTP, arcadedb-driver-grpc over gRPC), so I added a chooser. The index compared the bindings with the HTTP driver only, and the README had one sentence on the driver.

The README now has an "Embedded bindings or drivers?" block near the top: a 4-row table (what it is, needs a server, package and import name, use it when) with links to the HTTP and gRPC driver docs and to which-package.adoc. which-package.adoc has the full section "Embedded bindings or a driver?" with the same table, a three-line rule of thumb (including using both), a note that arcadedb is the embedded package and arcadedb-driver is the client, the gRPC plugin requirement, the Bolt, PostgreSQL, MongoDB and Redis note (standard clients, no ArcadeDB-specific one), and links to the driver pages of the main manual. The index and installation pages get one pointer sentence each, and the index section on the HTTP driver now mentions the gRPC driver.

This is prose and links only: no code block was added, so no docs page test changes, and there is no speed claim. I removed the old README paragraph on running the Docker image and arcadedb-driver because the new block covers it. I checked each docs.arcadedb.com and PyPI link target with curl -sI (all 200) and ran uvx pre-commit run --files on the four files (passes, including the old package name guard). The Docs workflow is the CI check for this change.

🤖 Generated with Claude Code