docs: rebrand the repository documentation, templates and dashboards

README, README_ZH, SECURITY, COMPLIANCE, CONTRIBUTING, NOTICE,
code_of_conduct, the vulnerability and PR-etiquette documents, the GitHub issue
and pull request templates, and the docs/ tree all present Silo as the product.
The Grafana dashboards under docs/metrics/prometheus/grafana/ have their panel
titles and descriptions rebranded while every minio_* query, label and
expression is left alone, so existing alerts and recording rules keep matching.

The distinction the review demanded is applied per hit rather than by
search-and-replace:

- Product and command text becomes Silo and silo: install and run instructions,
  systemd examples, compose services, download links, badges.
- Protocol and interface text keeps MinIO: MINIO_* variables, minio_* metrics,
  x-minio-* headers, /minio/* routes, .minio.sys, arn:minio, and API field and
  error names.
- Attribution keeps MinIO and gains the fork's own: the AGPL obligations,
  original copyright, CREDITS and NOTICE stay, with the modification notice
  added alongside rather than replacing them.
- Historical and third-party references are left as facts, not rewritten for
  brand tidiness.

README and README_ZH each carry an explicit non-affiliation notice, document
the side-by-side package migration including the
/etc/systemd/system/silo.service.d/10-legacy-user.conf drop-in for keeping a
legacy UID/GID, and state that recursive chown is never performed. The trademark
attribution uses the policy's approved "based on MinIO technology" wording, not
the shortened form the policy rejects.

github.com/pgsty/minio links are left in place and labelled transitional. The
repository has not been renamed, and rewriting them now would produce documented
URLs that 404 until the cutover; they change in the cutover commit together with
the goreleaser release target, the OCI source label and the raw-content branch.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

docs/chroot/README.md

@@ -1,4 +1,4 @@
-# Deploy MinIO on Chrooted Environment [![Slack](https://slack.min.io/slack?type=svg)](https://slack.min.io) [![Docker Pulls](https://img.shields.io/docker/pulls/minio/minio.svg?maxAge=604800)](https://hub.docker.com/r/minio/minio/)
+# Deploy Silo on Chrooted Environment [![Docker Pulls](https://img.shields.io/docker/pulls/pgsty/silo.svg?maxAge=604800)](https://hub.docker.com/r/pgsty/silo/)
 
 Chroot allows user based namespace isolation on many standard Linux deployments.
 
@@ -7,25 +7,24 @@ Chroot allows user based namespace isolation on many standard Linux deployments.
 - Familiarity with [chroot](http://man7.org/linux/man-pages/man2/chroot.2.html)
 - Chroot installed on your machine.
 
-## 2. Install MinIO in Chroot
+## 2. Install Silo in Chroot
 
-> **Note:** MinIO community edition is now distributed as source code only. Pre-compiled binaries are no longer provided for new releases.
-
-Build MinIO from source and install it in the chroot directory:
+Build Silo from source and install it in the chroot directory:
 
 ```sh
-# Build MinIO from source
-go install github.com/minio/minio@latest
+# From a checked-out Silo source tree
+go build -o silo .
 
 # Create the bin directory in your chroot
 mkdir -p /mnt/export/${USER}/bin
 
 # Copy the built binary to the chroot directory
-cp $(go env GOPATH)/bin/minio /mnt/export/${USER}/bin/minio
-chmod +x /mnt/export/${USER}/bin/minio
+cp ./silo /mnt/export/${USER}/bin/silo
+chmod +x /mnt/export/${USER}/bin/silo
 ```
 
-Alternatively, if you have an existing legacy binary, you can still use it, but note that it will not receive updates.
+Versioned binaries and native packages are also available from the
+[Silo download page](https://silo.pgsty.com/download/).
 
 Bind your `proc` mount to the target chroot directory
 
@@ -33,12 +32,12 @@ Bind your `proc` mount to the target chroot directory
 sudo mount --bind /proc /mnt/export/${USER}/proc
 ```
 
-## 3. Run Standalone MinIO in Chroot
+## 3. Run Standalone Silo in Chroot
 
 ### GNU/Linux
 
 ```sh
-sudo chroot --userspec username:group /mnt/export/${USER} /bin/minio --config-dir=/.minio server /data
+sudo chroot --userspec username:group /mnt/export/${USER} /bin/silo --config-dir=/.silo server /data
 
 Endpoint:  http://192.168.1.92:9000  http://65.19.167.92:9000
 AccessKey: MVPSPBW4NP2CMV1W3TXD
@@ -51,8 +50,8 @@ Instance is now accessible on the host at port 9000, proceed to access the Web b
 
 ## Explore Further
 
-- [MinIO Erasure Code Overview](https://silo.pgsty.com/operations/concepts/erasure-coding/)
-- [Use `mc` with MinIO Server](https://silo.pgsty.com/reference/minio-mc/)
-- [Use `aws-cli` with MinIO Server](https://silo.pgsty.com/integrations/aws-cli-with-minio/)
-- [Use `minio-go` SDK with MinIO Server](https://silo.pgsty.com/developers/go/minio-go/)
-- [The MinIO documentation website](https://silo.pgsty.com/docs/)
+- [Silo Erasure Code Overview](https://silo.pgsty.com/operations/concepts/erasure-coding/)
+- [Use `mc` with Silo Server](https://silo.pgsty.com/reference/minio-mc/)
+- [Use `aws-cli` with Silo Server](https://silo.pgsty.com/integrations/aws-cli-with-minio/)
+- [Use `minio-go` SDK with Silo Server](https://silo.pgsty.com/developers/go/minio-go/)
+- [The Silo documentation website](https://silo.pgsty.com/docs/)