S3 Vector Bucket: weed-vector ships in the image and the releases since 4.52

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011UpvafvK8JpagF94MHWqwK

S3-Vector-Bucket.md

@@ -53,7 +53,28 @@ The gateway serves all three bucket kinds on the S3 port. A vector bucket is a t
 
 ## Getting weed-vector
 
-No release or published Docker image includes `weed-vector` yet. Build it from source with Rust 1.94.1 or newer, running cargo inside `seaweed-vector/`. The workspace points Lance's build scripts at a bundled `protoc`, so no system `protoc` is needed:
+### Docker
+
+```bash
+docker run chrislusf/seaweedfs vector --masters master:9333 \
+  --storage-option aws_access_key_id=admin \
+  --storage-option aws_secret_access_key=admin-secret
+```
+
+Since release 4.52 the standard image carries the engine at `/usr/bin/weed-vector` on `amd64` and `arm64`, beside the Rust volume server and the Lance maintenance worker. The `vector` verb listens on `0.0.0.0:8090` unless `--listen` or `WEED_VECTOR_LISTEN` says otherwise, because the gateway dials it from another container. On `arm` and `386` the verb says the engine is not available for the platform.
+
+### From a release
+
+```bash
+curl -fsSL https://raw.githubusercontent.com/seaweedfs/seaweedfs/master/install.sh \
+  | bash -s -- --component vector
+```
+
+The assets are `weed-vector_linux_amd64.tar.gz` and `weed-vector_linux_arm64.tar.gz`, with md5s, on each GitHub release from 4.52 on. `--component all` installs it along with `weed`, the Rust volume server and the worker, and skips it on a platform or release that has no build. Linux only, like the worker.
+
+### From source
+
+Build it with Rust 1.94.1 or newer, running cargo inside `seaweed-vector/`. The workspace points Lance's build scripts at a bundled `protoc`, so no system `protoc` is needed:
 
 ```bash
 git clone https://github.com/seaweedfs/seaweedfs.git