Refactor validation process and update configuration examples

- Replaced the `validate-with-prefill.sh` script with a streamlined `make validate` command for improved usability.
- Updated `validate-config.yaml` to clarify cache management instructions and garbage collection algorithms.
- Enhanced comments to provide better guidance on upstream configurations and their implications for caching setups.

docs/examples/validate-config.yaml

@@ -22,7 +22,7 @@
 #
 # Usage (typical dev workflow):
 #   make build
-#   ./scripts/validate-with-prefill.sh
+#   make validate
 #   # In another terminal:
 #   SteamPrefill benchmark run -c 20 ...
 #
@@ -43,12 +43,15 @@ trusted_proxies: ["127.0.0.0/8"]
 cache:
   memory:
     size: 1GB
-    gc_algorithm: largest
+    gc_algorithm: hybrid
   disk:
     size: 2GB
-    path: ./validate-disk     # ephemeral; clean between runs if you want a fresh test
+    path: ./validate-disk     # cleaned between runs by make validate or make clean-disk
     gc_algorithm: hybrid      # recommended for disk in the project README
 
 # Empty upstream = use Host header from the client (SteamPrefill / real Steam clients).
-# This matches the common "DNS points lancache.steamcontent.com at the cache" setup.
+# Allows for chaining steamcache2 instances if needed.
+# For example, for a lan party you could have a small fast ram only cache at each table pointing to a larger slower disk cache in the back somewhere
+# It would reduce the amount of bandwidth needed to the internet and the amount needed to each table
+# just as a little reminder there is no authentication so this is not a good idea for a public cache just out on the internet.
 upstream: ""